Published November 6, 2017 | Updated November 8, 2017
The Android Security Bulletin contains details of security vulnerabilities
affecting Android devices. Security patch levels of 2017-11-06 or later address
all of these issues. To learn how to check a device's security patch level, see
Check and update
your Android version
.
Android partners were notified of all issues in the 2017-11-01 and 2017-11-05
patch levels at least a month before publication. Android partners were notified
of all issues in the 2017-11-06 patch level within the last month. Source code
patches for these issues have been released to the Android Open Source Project
(AOSP) repository and linked from this bulletin. This bulletin also includes
links to patches outside of AOSP.
The most severe of these issues is a critical security vulnerability in Media
framework that could enable a remote attacker using a specially crafted file to
execute arbitrary code within the context of a privileged process. The
severity
assessment
is based on the effect that exploiting the vulnerability would
possibly have on an affected device, assuming the platform and service
mitigations are turned off for development purposes or if successfully bypassed.
We have had no reports of active customer exploitation or abuse of these newly
reported issues. Refer to the
Android and Google Play
Protect mitigations
section for details on the
Android
security platform protections
and Google Play Protect, which improve the
security of the Android platform.
Note:
Information on the latest over-the-air update (OTA) and
firmware images for Google devices is available in the
November 2017
Pixel / Nexus Security Bulletin
.
Announcements
- We have launched a new
Pixel / Nexus Security
Bulletin
, which contains information on additional security
vulnerabilities and functional improvements that are addressed on supported
Pixel and Nexus devices. Android device manufacturers may choose to address
these issues on their devices. See
Common questions and
answers
for additional information.
- Security patches for the KRACK vulnerabilities are provided under the
2017-11-06 security patch level.
Android and Google service mitigations
This is a summary of the mitigations provided by the
Android
security platform
and service protections such as
Google Play Protect
. These
capabilities reduce the likelihood that security vulnerabilities could be
successfully exploited on Android.
- Exploitation for many issues on Android is made more difficult by
enhancements in newer versions of the Android platform. We encourage all users
to update to the latest version of Android where possible.
- The Android security team actively monitors for abuse through
Google Play Protect
and warns
users about
Potentially
Harmful Applications
. Google Play Protect is enabled by default on devices
with
Google Mobile Services
, and is
especially important for users who install apps from outside of Google
Play.
2017-11-01 security patch level?Vulnerability details
In the sections below, we provide details for each of the security
vulnerabilities that apply to the 2017-11-01 patch level. Vulnerabilities are
grouped under the component that they affect. There is a description of the
issue and a table with the CVE, associated references,
type of vulnerability
,
severity
,
and updated AOSP versions (where applicable). When available, we link the public
change that addressed the issue to the bug ID, like the AOSP change list. When
multiple changes relate to a single bug, additional references are linked to
numbers following the bug ID.
Framework
The most severe vulnerability in this section could enable a local malicious
application to bypass user interaction requirements in order to gain access to
additional permissions.
CVE
|
References
|
Type
|
Severity
|
Updated AOSP versions
|
CVE-2017-0830
|
A-62623498
|
EoP
|
High
|
6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0
|
CVE-2017-0831
|
A-37442941
[
2
]
|
EoP
|
High
|
8.0
|
The most severe vulnerability in this section could enable a remote attacker
using a specially crafted file to execute arbitrary code within the context of
a privileged process.
CVE
|
References
|
Type
|
Severity
|
Updated AOSP versions
|
CVE-2017-0832
|
A-62887820
|
RCE
|
Critical
|
6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0
|
CVE-2017-0833
|
A-62896384
|
RCE
|
Critical
|
6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0
|
CVE-2017-0834
|
A-63125953
|
RCE
|
Critical
|
6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0
|
CVE-2017-0835
|
A-63316832
|
RCE
|
Critical
|
6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0
|
CVE-2017-0836
|
A-64893226
|
RCE
|
Critical
|
5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0
|
CVE-2017-0839
|
A-64478003
|
ID
|
High
|
5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0
|
CVE-2017-0840
|
A-62948670
|
ID
|
High
|
5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0
|
System
The most severe vulnerability in this section could enable a remote attacker
using a specially crafted file to execute arbitrary code within the context of
a privileged process.
CVE
|
References
|
Type
|
Severity
|
Updated AOSP versions
|
CVE-2017-0841
|
A-37723026
|
RCE
|
Critical
|
5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0
|
CVE-2017-0842
|
A-37502513
|
EoP
|
High
|
6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0
|
2017-11-05 security patch level?Vulnerability details
In the sections below, we provide details for each of the security
vulnerabilities that apply to the 2017-11-05 patch level. Vulnerabilities are
grouped under the component that they affect and include details such as the
CVE, associated references,
type
of vulnerability
,
severity
,
component (where applicable), and updated AOSP versions (where applicable). When
available, we link the public change that addressed the issue to the bug ID,
like the AOSP change list. When multiple changes relate to a single bug,
additional references are linked to numbers following the bug ID.
Kernel components
The most severe vulnerability in this section could enable a local malicious
application to execute arbitrary code within the context of a privileged
process.
CVE
|
References
|
Type
|
Severity
|
Component
|
CVE-2017-9077
|
A-62265013
Upstream kernel
|
EoP
|
High
|
Networking subsystem
|
CVE-2017-7541
|
A-64258073
Upstream kernel
|
EoP
|
High
|
WLAN
|
The most severe vulnerability in this section could enable a local malicious
application to execute arbitrary code within the context of a privileged
process.
CVE
|
References
|
Type
|
Severity
|
Component
|
CVE-2017-0843
|
A-62670819
*
M-ALPS03361488
|
EoP
|
High
|
CCCI
|
NVIDIA components
The most severe vulnerability in this section could enable a local malicious
application to execute arbitrary code within the context of a privileged
process.
CVE
|
References
|
Type
|
Severity
|
Component
|
CVE-2017-6264
|
A-34705430
*
N-CVE-2017-6264
|
EoP
|
High
|
GPU driver
|
Qualcomm components
The most severe vulnerability in this section could enable a remote attacker
using a specially crafted file to execute arbitrary code within the context of
a privileged process.
CVE
|
References
|
Type
|
Severity
|
Component
|
CVE-2017-11013
|
A-64453535
QC-CR#2058261
[
2
]
|
RCE
|
Critical
|
WLAN
|
CVE-2017-11015
|
A-64438728
QC-CR#2060959
[
2
]
|
RCE
|
Critical
|
WLAN
|
CVE-2017-11014
|
A-64438727
QC-CR#2060959
|
RCE
|
Critical
|
WLAN
|
CVE-2017-11092
|
A-62949902
*
QC-CR#2077454
|
EoP
|
High
|
GPU driver
|
CVE-2017-9690
|
A-36575870
*
QC-CR#2045285
|
EoP
|
High
|
QBT1000 driver
|
CVE-2017-11017
|
A-64453575
QC-CR#2055629
|
EoP
|
High
|
Linux boot
|
CVE-2017-11028
|
A-64453533
QC-CR#2008683
[
2
]
|
ID
|
High
|
Camera
|
2017-11-06 security patch level?Vulnerability details
In the sections below, we provide details for each of the security
vulnerabilities that apply to the 2017-11-06 patch level. Vulnerabilities are
grouped under the component that they affect and include details such as the
CVE, associated references,
type of vulnerability
,
severity
,
component (where applicable), and updated AOSP versions (where applicable). When
available, we link the public change that addressed the issue to the bug ID,
like the AOSP change list. When multiple changes relate to a single bug,
additional references are linked to numbers following the bug ID.
System
The most severe vulnerability in this section could enable a proximate attacker
to bypass user interaction requirements before joining an unsecured Wi-Fi
network.
CVE
|
References
|
Type
|
Severity
|
Updated AOSP versions
|
CVE-2017-13077
|
A-67737262
|
EoP
|
High
|
5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0
|
CVE-2017-13078
|
A-67737262
|
EoP
|
High
|
5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0
|
CVE-2017-13079
|
A-67737262
|
EoP
|
High
|
5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0
|
CVE-2017-13080
|
A-67737262
|
EoP
|
High
|
5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0
|
CVE-2017-13081
|
A-67737262
|
EoP
|
High
|
5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0
|
CVE-2017-13082
|
A-67737262
|
EoP
|
High
|
7.0, 7.1.1, 7.1.2, 8.0
|
CVE-2017-13086
|
A-67737262
|
EoP
|
High
|
5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0
|
CVE-2017-13087
|
A-67737262
|
EoP
|
High
|
5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0
|
CVE-2017-13088
|
A-67737262
|
EoP
|
High
|
5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0
|
Note
: Android partners may also need to obtain fixes from
chipset manufacturers where applicable.
Common questions and answers
This section answers common questions that may occur after reading this
bulletin.
1. How do I determine if my device is updated to address these issues?
To learn how to check a device's security patch level, see
Check
& update your Android version
.
- Security patch levels of 2017-11-01 or later address all issues associated
with the 2017-11-01 security patch level.
- Security patch levels of 2017-11-05 or later address all issues associated
with the 2017-11-05 security patch level and all previous patch levels.
- Security patch levels of 2017-11-06 or later address all issues associated
with the 2017-11-06 security patch level and all previous patch levels.
Device manufacturers that include these updates should set the patch string
level to:
- [ro.build.version.security_patch]:[2017-11-01]
- [ro.build.version.security_patch]:[2017-11-05]
- [ro.build.version.security_patch]:[2017-11-06]
2. Why does this bulletin have three security patch levels?
This bulletin has three security patch levels so that Android partners have the
flexibility to fix a subset of vulnerabilities that are similar across all
Android devices more quickly. Android partners are encouraged to fix all issues
in this bulletin and use the latest security patch level.
- Devices that use the 2017-11-01 security patch level must include all issues
associated with that security patch level, as well as fixes for all issues
reported in previous security bulletins.
- Devices that use the 2017-11-05 security patch level must include all issues
associated with that security patch level, the 2017-11-01 security patch level,
as well as fixes for all issues reported in previous security bulletins.
- Devices that use the security patch level of 2017-11-06 or newer must
include all applicable patches in this (and previous) security
bulletins.
Partners are encouraged to bundle the fixes for all issues they are addressing
in a single update.
3. What do the entries in the
Type
column mean?
Entries in the
Type
column of the vulnerability details table reference
the classification of the security vulnerability.
Abbreviation
|
Definition
|
RCE
|
Remote code execution
|
EoP
|
Elevation of privilege
|
ID
|
Information disclosure
|
DoS
|
Denial of service
|
N/A
|
Classification not available
|
4. What do the entries in the
References
column mean?
Entries under the
References
column of the vulnerability details table
may contain a prefix identifying the organization to which the reference value
belongs.
Prefix
|
Reference
|
A-
|
Android bug ID
|
QC-
|
Qualcomm reference number
|
M-
|
MediaTek reference number
|
N-
|
NVIDIA reference number
|
B-
|
Broadcom reference number
|
5. What does a * next to the Android bug ID in the
References
column mean?
Issues that are not publicly available have a * next to the Android bug ID in
the
References
column. The update for that issue is generally contained
in the latest binary drivers for Nexus devices available from the
Google Developer
site
.
6. Why are security vulnerabilities split between this bulletin and
device/partner security bulletins, such as the Pixel / Nexus bulletin?
Security vulnerabilities that are documented in this security bulletin are
required in order to declare the latest security patch level on Android devices.
Additional security vulnerabilities that are documented in the device/partner
security bulletins are not required for declaring a security patch level.
Android device and chipset manufacturers are encouraged to document the presence
of other fixes on their devices through their own security websites, such as the
Samsung
,
LGE
, or
Pixel / Nexus
security bulletins.
Versions
Version
|
Date
|
Notes
|
1.0
|
November 6, 2017
|
Bulletin published.
|
1.1
|
November 8, 2017
|
Bulletin revised to include AOSP links.
|