Published January 2, 2018 | Updated January 29, 2018
The Pixel / Nexus Security Bulletin contains details of security vulnerabilities and functional improvements affecting supported Google Pixel and Nexus devices (Google devices). For Google devices, security patch levels of 2018-01-05 or later address all issues in this bulletin and all issues in the January 2018 Android Security Bulletin. To learn how to check a device's security patch level, see Check and update your Android version.
All supported Google devices will receive an update to the 2018-01-05 patch level. We encourage all customers to accept these updates to their devices.
Note: The Google device firmware images are available on the Google Developer site.
Announcements
In addition to the security vulnerabilities described in the January 2018 Android Security Bulletin, Pixel and Nexus devices also contain patches for the security vulnerabilities described below. Partners were notified of these issues at least a month ago and may choose to incorporate them as part of their device updates.
Security patches
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 Android Open Source Project (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
CVE | References | Type | Severity | Updated AOSP versions |
---|---|---|---|---|
CVE-2017-0846 | A-64934810 [2] | ID | Moderate | 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0 |
Media framework
CVE | References | Type | Severity | Updated AOSP versions |
---|---|---|---|---|
CVE-2017-13201 | A-63982768 | ID | Moderate | 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1 |
CVE-2017-13202 | A-67647856 | ID | Moderate | 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1 |
CVE-2017-13206 | A-65025048 | ID | Moderate | 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1 |
CVE-2017-13207 | A-37564426 | ID | Moderate | 7.0, 7.1.1, 7.1.2, 8.0 |
CVE-2017-13185 | A-65123471 | ID | Moderate | 7.0, 7.1.1, 7.1.2, 8.0 |
DoS | High | 5.1.1, 6.0, 6.0.1 | ||
CVE-2017-13187 | A-65034175 | ID | Moderate | 7.0, 7.1.1, 7.1.2, 8.0, 8.1 |
DoS | High | 5.1.1, 6.0, 6.0.1 | ||
CVE-2017-13188 | A-65280786 | ID | Moderate | 7.0, 7.1.1, 7.1.2, 8.0, 8.1 |
DoS | High | 5.1.1, 6.0, 6.0.1 | ||
CVE-2017-13203 | A-63122634 | ID | Moderate | 7.0, 7.1.1, 7.1.2, 8.0, 8.1 |
DoS | High | 6.0, 6.0.1 | ||
CVE-2017-13204 | A-64380237 | ID | Moderate | 7.0, 7.1.1, 7.1.2, 8.0, 8.1 |
DoS | High | 6.0, 6.0.1 | ||
CVE-2017-13205 | A-64550583 | ID | Moderate | 7.0, 7.1.1, 7.1.2, 8.0, 8.1 |
DoS | High | 6.0, 6.0.1 | ||
CVE-2017-13200 | A-63100526 | ID | Low | 7.0, 7.1.1, 7.1.2, 8.0, 8.1 |
ID | Moderate | 5.1.1, 6.0, 6.0.1 | ||
CVE-2017-13186 | A-65735716 | NSI | NSI | 7.0, 7.1.1, 7.1.2, 8.0, 8.1 |
DoS | High | 6.0, 6.0.1 | ||
CVE-2017-13189 | A-68300072 | NSI | NSI | 7.0, 7.1.1, 7.1.2, 8.0, 8.1 |
DoS | High | 6.0.1 | ||
CVE-2017-13190 | A-68299873 | NSI | NSI | 7.0, 7.1.1, 7.1.2, 8.0, 8.1 |
DoS | High | 6.0.1 | ||
CVE-2017-13194 | A-64710201 | NSI | NSI | 7.0, 7.1.1, 7.1.2, 8.0, 8.1 |
DoS | High | 5.1.1, 6.0, 6.0.1 | ||
CVE-2017-13198 | A-68399117 | NSI | NSI | 7.0, 7.1.1, 7.1.2, 8.0, 8.1 |
DoS | High | 5.1.1, 6.0, 6.0.1 |
System
CVE | References | Type | Severity | Updated AOSP versions |
---|---|---|---|---|
CVE-2017-13212 | A-62187985 | EoP | Moderate | 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0 |
Broadcom components
CVE | References | Type | Severity | Component |
---|---|---|---|---|
CVE-2017-13213 | A-63374465* B-V2017081501 |
EoP | Moderate | Bcmdhd driver |
HTC components
CVE | References | Type | Severity | Component |
---|---|---|---|---|
CVE-2017-11072 | A-65468991* | EoP | Moderate | Partition table updater |
Kernel components
CVE | References | Type | Severity | Component |
---|---|---|---|---|
CVE-2017-13219 | A-62800865* | DoS | Moderate | Synaptics touchscreen controller |
CVE-2017-13220 | A-63527053* | EoP | Moderate | BlueZ |
CVE-2017-13221 | A-64709938* | EoP | Moderate | Wifi driver |
CVE-2017-11473 | A-64253928 Upstream kernel |
EoP | Moderate | Kernel |
CVE-2017-13222 | A-38159576* | ID | Moderate | Kernel |
CVE-2017-14140 | A-65468230 Upstream kernel |
ID | Moderate | Kernel |
CVE-2017-15537 | A-68805943 Upstream kernel |
ID | Moderate | Kernel |
MediaTek components
CVE | References | Type | Severity | Component |
---|---|---|---|---|
CVE-2017-13225 | A-38308024* M-ALPS03495789 |
EoP | High | MTK Media |
CVE | References | Type | Severity | Component |
---|---|---|---|---|
CVE-2017-13226 | A-32591194* M-ALPS03149184 |
EoP | Moderate | MTK |
Qualcomm components
CVE | References | Type | Severity | Component |
---|---|---|---|---|
CVE-2017-9705 | A-67713091 QC-CR#2059828 |
EoP | Moderate | SOC Driver |
CVE-2017-15847 | A-67713087 QC-CR#2070309 |
EoP | Moderate | SOC Driver |
CVE-2017-15848 | A-67713083 QC-CR#2073777 |
EoP | Moderate | Driver |
CVE-2017-11081 | A-67713113 QC-CR#2077622 |
EoP | Moderate | WLan |
CVE-2017-15845 | A-67713111 QC-CR#2072966 |
EoP | Moderate | WLan |
CVE-2017-14873 | A-67713104 QC-CR#2057144 [ 2] |
EoP | Moderate | Graphics Driver |
CVE-2017-11035 | A-67713108 QC-CR#2070583 |
EoP | Moderate | Wireless driver |
CVE-2017-11003 | A-64439673 QC-CR#2026193 |
EoP | Moderate | Bootloader |
CVE-2017-9689 | A-62828527 QC-CR#2037019 |
EoP | Moderate | HDMI driver |
CVE-2017-14879 | A-63890276* QC-CR#2056307 |
EoP | Moderate | IPA driver |
CVE-2017-11080 | A-66937382 QC-CR#2078272 |
EoP | Moderate | Bootloader |
CVE-2017-14869 | A-67713093 QC-CR#2061498 |
ID | Moderate | Bootloader |
CVE-2017-11066 | A-65468971 QC-CR#2068506 |
ID | Moderate | Bootloader |
CVE-2017-15850 | A-62464339* QC-CR#2113240 |
ID | Moderate | Microphone driver |
CVE-2017-9712 | A-63868883 QC-CR#2033195 |
ID | Moderate | Wireless driver |
CVE-2017-11079 | A-67713100 QC-CR#2078342 |
ID | Moderate | Bootloader |
CVE-2017-14870 | A-67713096 QC-CR#2061506 |
ID | Moderate | Bootloader |
CVE-2017-11079 | A-66937383 QC-CR#2078342 |
ID | Moderate | Bootloader |
Functional updates
These updates are included for affected Pixel devices to address functionality issues not related to the security of Pixel devices. The table includes associated references; the affected category, such as Bluetooth or mobile data; and improvements.
References | Category | Improvements |
---|---|---|
A-68810306 | Keystore | Adjusted handling of key upgrades in keystore. |
A-70213235 | Stability | Improve stability and performance after installing an OTA. |
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?
Security patch levels of 2018-01-05 or later address all issues associated with the 2018-01-05 security patch level and all previous patch levels. To learn how to check a device's security patch level, read the instructions on the Pixel and Nexus update schedule.
2. 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 |
3. 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 |
4. 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.
5. Why are security vulnerabilities split between this bulletin and the Android Security Bulletins?
Security vulnerabilities that are documented in the Android Security Bulletins are required in order to declare the latest security patch level on Android devices. Additional security vulnerabilities, such as those documented in this bulletin, are not required for declaring a security patch level.
Versions
Version | Date | Notes |
---|---|---|
1.0 | January 2, 2018 | Bulletin published. |
1.1 | January 5, 2018 | Bulletin revised to include AOSP links. |
1.2 | January 29, 2018 | Added CVE-2017-13225. |