自 2025 年 3 月 27 日起，我们建议您使用 android-latest-release 而非 aosp-main 构建 AOSP 并为其做出贡献。如需了解详情，请参阅 AOSP 的变更。
Pixel/Nexus 安全公告 - 2018 年 12 月
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
发布时间：2018 年 12 月 3 日
本 Pixel/Nexus 安全公告详细介绍了会影响受支持的 Google Pixel 和 Nexus 设备（Google 设备）的安全漏洞和功能改进。
对于 Google 设备，如果安全补丁级别是 2018-12-05 或更新，则意味着已解决本公告以及 2018 年 12 月的 Android 安全公告中所述的所有问题。如需了解如何查看设备的安全补丁级别，请参阅查看并更新 Android 版本。
所有受支持的 Google 设备都将会收到 2018-12-05 补丁级别的更新。建议所有用户都在自己的设备上接受这些更新。
注意：Google Developers 网站上提供 Google 设备固件映像。
通告
除了 2018 年 12 月的 Android 安全公告中所述的安全漏洞外，Google 设备中还包含针对下述安全漏洞的补丁。
安全补丁
漏洞列在所影响的组件下，内容包括问题描述和一个表，该表中包含 CVE、相关参考编号、漏洞类型、严重程度和已更新的 Android 开源项目 (AOSP) 版本（若有）。如果有解决相应问题的公开更改记录（例如 AOSP 代码更改列表），我们会将 Bug ID 链接到该记录。如果某个 bug 有多条相关的代码更改记录，我们还会通过 bug ID 后面的数字链接到更多参考内容。
Qualcomm 组件
| CVE |
参考编号 |
类型 |
严重程度 |
组件 |
| CVE-2018-11987 |
A-70638103
QC-CR#2258691 |
EoP |
中 |
ION |
功能补丁
我们针对受影响的 Pixel 设备纳入了以下功能补丁程序，以解决与 Pixel 设备安全性无关的功能问题。下表中列出的补丁包含相关参考编号、受影响的类别和受影响的设备。
| 参考编号 |
类别 |
改进 |
设备 |
| A-112646910 |
安全性 |
改进了重置后的图案解锁识别效果 |
Pixel、Pixel XL |
| A-117522738 |
性能 |
改进了在某些情形下的内存性能 |
Pixel 2、Pixel 2 XL、Pixel 3、Pixel 3 XL |
| A-110969183 |
相机 |
改进了相机拍摄性能 |
Pixel 2、Pixel 2 XL、Pixel 3、Pixel 3 XL |
| A-111008450 |
Pixel Stand |
改进了使用 Pixel Stand 时的通知可见性 |
Pixel 3、Pixel 3 XL |
| A-112376366 |
Android Auto |
改进了 Android Auto 的兼容性 |
Pixel 2、Pixel 2 XL、Pixel 3、Pixel 3 XL |
| A-115666282 |
相机 |
调整了自动对焦行为 |
Pixel 3、Pixel 3 XL |
| A-115624433 |
Pixel Stand |
改进了使用 Pixel Stand 时的启动指令性能 |
Pixel 3、Pixel 3 XL |
| A-116758282 |
显示 |
改进了“显示屏始终保持开启状态”的触发性能 |
Pixel 3、Pixel 3 XL |
| A-111964925 |
音频 |
改进了 USB-C 音频配件检测 |
Pixel 3 XL |
| A-111716107 |
蓝牙 |
调整了切换蓝牙时的音量行为 |
Pixel、Pixel XL、Pixel 2、Pixel 2 XL、Pixel 3、Pixel 3 XL |
| A-111159723 |
Android Auto |
改进了在某些车辆中使用 Android Auto 时的音频性能 |
Pixel 3、Pixel 3 XL |
| A-112228430 |
媒体 |
改进了某些媒体应用上的 HDR 颜色轮廓 |
Pixel 3、Pixel 3 XL |
| A-113151604 |
相机 |
改进了相机快门性能 |
Pixel 3、Pixel 3 XL |
| A-111277984 |
性能 |
改进使用蓝牙时的解锁性能 |
Pixel、Pixel XL、Pixel 2、Pixel 2 XL、Pixel 3、Pixel 3 XL |
常见问题和解答
这一部分解答了用户在阅读本公告后可能会提出的常见问题。
1. 如何确定我的设备是否已通过更新解决这些问题？
如果安全补丁级别是 2018-12-05 或更新，则意味着已解决 2018-12-05 以及之前的所有安全补丁级别涵盖的所有问题。如需了解如何查看设备的安全补丁级别，请参阅 Pixel 和 Nexus 更新时间表中的说明。
2. “类型”列中的条目表示什么意思？
在漏洞详情表内，“类型”列中的条目是安全漏洞的分类。
| 缩写词 |
定义 |
| RCE |
远程代码执行 |
| EoP |
提权 |
| ID |
信息披露 |
| DoS |
拒绝服务攻击 |
| N/A |
没有分类 |
3. “参考编号”列中的条目表示什么意思？
在漏洞详情表内，“参考编号”列中的条目可能包含用于标识参考编号值所属组织的前缀。
| 前缀 |
参考编号 |
| A- |
Android bug ID |
| QC- |
Qualcomm 参考编号 |
| M- |
MediaTek 参考编号 |
| N- |
NVIDIA 参考编号 |
| B- |
Broadcom 参考编号 |
4. 在“参考编号”列中，Android bug ID 旁边的 * 表示什么意思？
如果问题尚未公开发布，在“参考编号”列中，相应 Android bug ID 旁边会显示 *。Google Developers 网站上针对 Pixel/Nexus 设备提供的最新二进制驱动程序中通常包含用于解决相应问题的更新。
5. 为什么要将安全漏洞拆分到本公告和 Android 安全公告中？
如需声明 Android 设备的最新安全补丁程序级别，必须修复 Android 安全公告中记录的安全漏洞，但在声明安全补丁程序级别时，并不是必须要修复其他安全漏洞（如本公告中记录的漏洞）。
版本
| 版本 |
日期 |
备注 |
| 1.0 |
2018 年 12 月 3 日 |
发布了本公告。 |
本页面上的内容和代码示例受内容许可部分所述许可的限制。Java 和 OpenJDK 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-08-07。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["没有我需要的信息","missingTheInformationINeed","thumb-down"],["太复杂/步骤太多","tooComplicatedTooManySteps","thumb-down"],["内容需要更新","outOfDate","thumb-down"],["翻译问题","translationIssue","thumb-down"],["示例/代码问题","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-07。"],[],[],null,["# Pixel / Nexus Security Bulletin—December 2018\n\n*Published December 3, 2018*\n\n\nThe Pixel / Nexus Security Bulletin contains details of security\nvulnerabilities and functional improvements affecting [supported Google Pixel and Nexus devices](https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices) (Google devices).\nFor Google devices, security patch levels of 2018-12-05 or later address all\nissues in this bulletin and all issues in the December 2018 Android Security\nBulletin. To learn how to check a device's security patch level, see [Check \\& update your Android version](https://support.google.com/pixelphone/answer/4457705).\n\n\nAll supported Google devices will receive an update to the 2018-12-05 patch\nlevel. We encourage all customers to accept these updates to their devices.\n\n\n**Note:** The Google device firmware images are available on the\n[Google\nDeveloper site](https://developers.google.com/android/images).\n\nAnnouncements\n-------------\n\nIn addition to the security vulnerabilities described in the\n[December 2018 Android Security\nBulletin](/docs/security/bulletin/2018-12-01), Google devices also contain patches for the security\nvulnerabilities described below.\n\nSecurity patches\n----------------\n\n\nVulnerabilities are grouped under the component they affect. There is a\ndescription of the issue and a table with the CVE, associated references,\n[type of vulnerability](#type),\n[severity](/docs/security/overview/updates-resources#severity),\nand updated Android Open Source Project (AOSP) versions (where applicable).\nWhen available, we link the public change that addressed the issue to the bug\nID, such as the AOSP change list. When multiple changes relate to a single bug,\nadditional references are linked to numbers following the bug ID.\n\n### Qualcomm components\n\n| CVE | References | Type | Severity | Component |\n|----------------|--------------------------------------------------------------------------------------------------------------------------------------|------|----------|-----------|\n| CVE-2018-11987 | A-70638103 [QC-CR#2258691](https://source.codeaurora.org/quic/la/kernel/msm-4.9/commit/?id=5e9ffcfa152ecb2832990c42fcd8a0f2e63c2c04) | EoP | Moderate | ION |\n\nFunctional patches\n------------------\n\nThe functional patches are included for affected Pixel devices to address\nfunctionality issues not related to the security of Pixel devices. The patches\nlisted in the table below include associated references, the affected category,\nand the affected devices.\n\n| References | Category | Improvements | Devices |\n|-------------|--------------|----------------------------------------------------------------------------|-----------------------------------------------------------|\n| A-112646910 | Security | Improved pattern unlock recognition after reset | Pixel, Pixel XL |\n| A-117522738 | Performance | Improved memory performance in certain circumstances | Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL |\n| A-110969183 | Camera | Improved camera capture performance | Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL |\n| A-111008450 | Pixel Stand | Improved notification visibility when using Pixel Stand | Pixel 3, Pixel 3 XL |\n| A-112376366 | Android Auto | Improved Android Auto compatibility | Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL |\n| A-115666282 | Camera | Adjusted autofocus behavior | Pixel 3, Pixel 3 XL |\n| A-115624433 | Pixel Stand | Improved hotword performance when using Pixel Stand | Pixel 3, Pixel 3 XL |\n| A-116758282 | Display | Improved Always On Display triggering | Pixel 3, Pixel 3 XL |\n| A-111964925 | Audio | Improved USB-C Audio accessory detection | Pixel 3 XL |\n| A-111716107 | Bluetooth | Adjusted volume behavior when toggling Bluetooth | Pixel, Pixel XL, Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL |\n| A-111159723 | Android Auto | Improved audio performance for when using Android Auto in certain vehicles | Pixel 3, Pixel 3 XL |\n| A-112228430 | Media | Improved contouring on HDR color on certain media apps | Pixel 3, Pixel 3 XL |\n| A-113151604 | Camera | Improved camera shutter performance | Pixel 3, Pixel 3 XL |\n| A-111277984 | Performance | Improve unlocking performance when using Bluetooth | Pixel, Pixel XL, Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL |\n\nCommon questions and answers\n----------------------------\n\n\nThis section answers common questions that may occur after reading this\nbulletin.\n\n\n**1. How do I determine if my device is updated to address these issues?**\n\n\nSecurity patch levels of 2018-12-05 or later address all issues associated with\nthe 2018-12-05 security patch level and all previous patch levels. To learn how\nto check a device's security patch level, read the instructions on the [Pixel and Nexus update schedule](https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices).\n\n\n**2. What do the entries in the *Type* column mean?**\n\n\nEntries in the *Type* column of the vulnerability details table reference\nthe classification of the security vulnerability.\n\n| Abbreviation | Definition |\n|--------------|------------------------------|\n| RCE | Remote code execution |\n| EoP | Elevation of privilege |\n| ID | Information disclosure |\n| DoS | Denial of service |\n| N/A | Classification not available |\n\n\n**3. What do the entries in the *References* column mean?**\n\n\nEntries under the *References* column of the vulnerability details table\nmay contain a prefix identifying the organization to which the reference value\nbelongs.\n\n| Prefix | Reference |\n|--------|---------------------------|\n| A- | Android bug ID |\n| QC- | Qualcomm reference number |\n| M- | MediaTek reference number |\n| N- | NVIDIA reference number |\n| B- | Broadcom reference number |\n\n\n**4. What does a \\* next to the Android bug ID in the *References*\ncolumn mean?**\n\n\nIssues that are not publicly available have a \\* next to the Android bug ID in\nthe *References* column. The update for that issue is generally contained\nin the latest binary drivers for Pixel / Nexus devices available\nfrom the [Google Developer site](https://developers.google.com/android/drivers).\n\n\n**5. Why are security vulnerabilities split between this bulletin and the\nAndroid Security Bulletins?**\n\n\nSecurity vulnerabilities that are documented in the Android Security Bulletins\nare required to declare the latest security patch level on Android\ndevices. Additional security vulnerabilities, such as those documented in this\nbulletin are not required for declaring a security patch level.\n\nVersions\n--------\n\n| Version | Date | Notes |\n|---------|------------------|---------------------|\n| 1.0 | December 3, 2018 | Bulletin published. |"]]
