Published March 5, 2018 | Updated March 7, 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-03-05 or later address all issues in this bulletin and all issues in the March 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-03-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 March 2018 Android Security Bulletin, Google 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-13263 | A-69383160 [2] | EoP | Moderate | 8.0, 8.1 |
Media framework
| CVE | References | Type | Severity | Updated AOSP versions |
|---|---|---|---|---|
| CVE-2017-13264 | A-70294343 | NSI | NSI | 7.0, 7.1.1, 7.1.2, 8.0, 8.1 |
| DoS | High | 6.0, 6.0.1 | ||
| CVE-2017-13254 | A-70239507 | 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-13265 | A-36232423 [2] [3] | EoP | Moderate | 7.0, 7.1.1, 7.1.2, 8.0, 8.1 |
| CVE-2017-13268 | A-67058064 | ID | Moderate | 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1 |
| CVE-2017-13269 | A-68818034 | ID | Moderate | 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1 |
Kernel components
| CVE | References | Type | Severity | Component |
|---|---|---|---|---|
| CVE-2017-5754 | A-69856074* | ID | High | Memory mapping |
| CVE-2017-13270 | A-69474744* | EoP | Moderate | Mnh_sm driver |
| CVE-2017-13271 | A-69006799* | EoP | Moderate | Mnh_sm driver |
| CVE-2017-16527 | A-69051382 Upstream kernel |
EoP | Moderate | USB sound driver |
| CVE-2017-15649 | A-69160446 Upstream kernel [2] |
EoP | Moderate | Network driver |
| CVE-2017-1000111 | A-68806121 Upstream kernel |
EoP | Moderate | Network driver |
NVIDIA components
| CVE | References | Type | Severity | Component |
|---|---|---|---|---|
| CVE-2017-6287 | A-64893264* N-CVE-2017-6287 |
ID | Moderate | Media framework |
| CVE-2017-6285 | A-64893156* N-CVE-2017-6285 |
ID | Moderate | Media framework |
| CVE-2017-6288 | A-65482562* N-CVE-2017-6288 |
ID | Moderate | Media framework |
Qualcomm components
| CVE | References | Type | Severity | Component |
|---|---|---|---|---|
| CVE-2017-18061 | A-70237701 QC-CR#2117246 |
EoP | Moderate | Wil6210 |
| CVE-2017-18050 | A-70237697 QC-CR#2119443 |
EoP | Moderate | Wma management |
| CVE-2017-18054 | A-70237694 QC-CR#2119432 |
EoP | Moderate | Wma |
| CVE-2017-18055 | A-70237693 QC-CR#2119430 |
EoP | Moderate | Wma |
| CVE-2017-18065 | A-70237685 QC-CR#2113423 |
EoP | Moderate | Wma |
| CVE-2017-18066 | A-70235107 QC-CR#2107976 |
EoP | Moderate | Power driver |
| CVE-2017-18062 | A-68992451 QC-CR#2115375 |
EoP | Moderate | Wma |
| CVE-2018-3561 | A-68870904* QC-CR#2068569 |
EoP | Moderate | Diagchar |
| CVE-2018-3560 | A-68664502* QC-CR#2142216 |
EoP | Moderate | Qdsp6v2 sound driver |
| CVE-2017-15834 | A-70237704 QC-CR#2111858 |
EoP | Moderate | Diagchar |
| CVE-2017-15833 | A-70237702 QC-CR#2059835 |
EoP | Moderate | Power driver |
| CVE-2017-15831 | A-70237687 QC-CR#2114255 |
EoP | Moderate | Wma |
| CVE-2017-15830 | A-70237719 QC-CR#2120725 |
EoP | Moderate | sme driver |
| CVE-2017-14889 | A-70237700 QC-CR#2119803 |
EoP | Moderate | Wma |
| CVE-2017-14887 | A-70237715 QC-CR#2119673 |
EoP | Moderate | WLAN |
| CVE-2017-14879 | A-63851638* QC-CR#2056307 |
EoP | Moderate | IPA |
| CVE-2017-11082 | A-66937387 QC-CR#2071560 |
EoP | Moderate | WLAN |
| CVE-2017-11074 | A-68940798 QC-CR#2049138 |
EoP | Moderate | WLAN |
| CVE-2017-18052 | A-70237712 QC-CR#2119439 |
ID | Moderate | WLAN |
| CVE-2017-18057 | A-70237709 QC-CR#2119403 |
ID | Moderate | WLAN |
| CVE-2017-18059 | A-70237708 QC-CR#2119399 |
ID | Moderate | WLAN |
| CVE-2017-18060 | A-70237707 QC-CR#2119394 |
ID | Moderate | WLAN |
| CVE-2017-18051 | A-70237696 QC-CR#2119442 |
ID | Moderate | WLAN |
| CVE-2017-18053 | A-70237695 QC-CR#2119434 |
ID | Moderate | WLAN |
| CVE-2017-18058 | A-70237690 QC-CR#2119401 |
ID | Moderate | WLAN |
| CVE-2017-15855 | A-38232131* QC-CR#2025367 |
ID | Moderate | Camera_v2 driver |
| CVE-2017-15814 | A-64836865* QC-CR#2092793 |
ID | Moderate | Camera_v2 driver |
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; improvements; and affected devices.
| References | Category | Improvements | Devices |
|---|---|---|---|
| A-70491468 | Performance | Improve screen wake performance with fingerprint unlock | Pixel 2, Pixel 2 XL |
| A-69307875 | Audio | Improve audio performance when recording video | Pixel 2 XL |
| A-70641186 | Reporting | Improve crash reporting | Pixel 2, Pixel 2 XL |
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-03-05 or later address all issues associated with the 2018-03-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 | March 5, 2018 | Bulletin published. |
| 1.1 | March 7, 2018 | Bulletin revised to include AOSP links and update reference number for CVE-2017-15855. |