Android Security Bulletin—December 2016

Stay organized with collections Save and categorize content based on your preferences.

Published December 05, 2016 | Updated December 21, 2016

The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Alongside the bulletin, we have released a security update to Google devices through an over-the-air (OTA) update. The Google device firmware images have also been released to the Google Developer site. Security levels of December 05, 2016 or later address all of these issues. Refer to the Pixel and Nexus update schedule to learn how to check a device's security level.

Partners were notified of the issues described in the bulletin on November 07, 2016 or earlier. Source code es 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 es outside of AOSP.

The most severe of these issues are Critical security vulnerabilities in device-specific code that could enable arbitrary code execution within the context of the kernel, leading to the possibility of a local permanent device compromise, which may require reflashing the operating system to repair the device. 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 disabled 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 service mitigations section for details on the Android security platform protections and service protections such as SafetyNet, which improve the security of the Android platform.

We encourage all customers to accept these updates to their devices.

Announcements

• This bulletin has two security level strings to provide Android partners with the flexibility to more quickly fix a subset of vulnerabilities that are similar across all Android devices. See Common questions and answers for additional information:
  • 2016-12-01: Partial security level string. This security level string indicates that all issues associated with 2016-12-01 (and all previous security level strings) are addressed.
  • 2016-12-05: Complete security level string. This security level string indicates that all issues associated with 2016-12-01 and 2016-12-05 (and all previous security level strings) are addressed.
• Supported Google devices will receive a single OTA update with the December 05, 2016 security level.

Android and Google service mitigations

This is a summary of the mitigations provided by the Android security platform and service protections, such as SafetyNet. 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 with Verify Apps and SafetyNet, which are designed to warn users about Potentially Harmful Applications. Verify Apps is enabled by default on devices with Google Mobile Services and is especially important for users who install applications from outside of Google Play. Device rooting tools are prohibited within Google Play, but Verify Apps warns users when they attempt to install a detected rooting application—no matter where it comes from. Additionally, Verify Apps attempts to identify and block installation of known malicious applications that exploit a privilege escalation vulnerability. If such an application has already been installed, Verify Apps will notify the user and attempt to remove the detected application.
• As appropriate, Google Hangouts and Messenger applications do not automatically pass media to processes such as Mediaserver.

Acknowledgements

We would like to thank these researchers for their contributions:

• Baozeng Ding, Chengming Yang, Peng Xiao, Ning You, Yang Dong, Chao Yang, Yi Zhang, and Yang Song of Alibaba Mobile Security Group: CVE-2016-6783, CVE-2016-6784, CVE-2016-6785
• Chi Zhang, Mingjian Zhou (@Mingjian_Zhou), Chiachih Wu (@chiachih_wu), and Xuxian Jiang of C0RE Team: CVE-2016-6789, CVE-2016-6790
• Christian Seel: CVE-2016-6769
• David Benjamin and Kenny Root of Google: CVE-2016-6767
• Di Shen (@returnsme) of KeenLab (@keen_lab), Tencent: CVE-2016-6776, CVE-2016-6787
• En He (@heeeeen4x) of MS509Team: CVE-2016-6763
• Gengjia Chen (@chengjia4574), pjf of IceSword Lab, Qihoo 360 Technology Co. Ltd.: CVE-2016-6779, CVE-2016-6778, CVE-2016-8401, CVE-2016-8402, CVE-2016-8403, CVE-2016-8409, CVE-2016-8408, CVE-2016-8404
• Jianqiang Zhao (@jianqiangzhao) and pjf of IceSword Lab, Qihoo 360 Technology Co. Ltd: CVE-2016-6788, CVE-2016-6781, CVE-2016-6782, CVE-2016-8396
• Lubo Zhang, Tong Lin, Yuan-Tsung Lo, Chiachih Wu (@chiachih_wu), and Xuxian Jiang of C0RE Team: CVE-2016-6791, CVE-2016-8391, CVE-2016-8392
• Mark Brand of Project Zero: CVE-2016-6772
• Michał Bednarski: CVE-2016-6770, CVE-2016-6774
• Mingjian Zhou (@Mingjian_Zhou), Chi Zhang, Chiachih Wu (@chiachih_wu), and Xuxian Jiang of C0RE Team: CVE-2016-6761, CVE-2016-6759, CVE-2016-8400
• Mingjian Zhou (@Mingjian_Zhou), Chiachih Wu (@chiachih_wu), and Xuxian Jiang of C0RE Team: CVE-2016-6760
• Mingjian Zhou (@Mingjian_Zhou), Hanxiang Wen, Chiachih Wu (@chiachih_wu), and Xuxian Jiang of C0RE Team: CVE-2016-6759
• Nathan Crandall (@natecray) of Tesla Motors Product Security Team: CVE-2016-6915, CVE-2016-6916, CVE-2016-6917
• Nightwatch Cybersecurity Research (@nightwatchcyber): CVE-2016-5341
• Pengfei Ding (丁鹏飞), Chenfu Bao (包沉浮), Lenx Wei (韦韬) of Baidu X-Lab: CVE-2016-6755, CVE-2016-6756
• Peter Pi (@heisecode) of Trend Micro: CVE-2016-8397, CVE-2016-8405, CVE-2016-8406, CVE-2016-8407
• Qidan He (何淇丹) (@flanker_hqd) of KeenLab, Tencent (腾讯科恩实验室): CVE-2016-8399, CVE-2016-8395
• Qidan He (何淇丹) (@flanker_hqd) and Marco Grassi (@marcograss) of KeenLab, Tencent (腾讯科恩实验室): CVE-2016-6768
• Richard Shupak: CVE-2016-5341
• Sagi Kedmi of IBM X-Force Research: CVE-2016-8393, CVE-2016-8394
• Seven Shen (@lingtongshen) of Mobile Threat Research Team, Trend Micro Inc.: CVE-2016-6757
• Weichao Sun (@sunblate) of Alibaba Inc.: CVE-2016-6773
• Wenke Dou, Chi Zhang, Chiachih Wu (@chiachih_wu), and Xuxian Jiang of C0RE Team: CVE-2016-6765
• Wish Wu (@wish_wu) (吴潍浠) of Mobile Threat Response Team, Trend Micro Inc.: CVE-2016-6704
• Yuan-Tsung Lo, Tong Lin, Chiachih Wu (@chiachih_wu), and Xuxian Jiang of C0RE Team: CVE-2016-6786, CVE-2016-6780, CVE-2016-6775
• Yuan-Tsung Lo, Xiaodong Wang, Chiachih Wu (@chiachih_wu), and Xuxian Jiang of C0RE Team: CVE-2016-6777
• Yuxiang Li of Tencent Security Platform Department: CVE-2016-6771
• Zhe Jin (金哲) of Chengdu Security Response Center, Qihoo 360 Technology Co. Ltd.: CVE-2016-6764, CVE-2016-6766
• Zinuo Han of Chengdu Security Response Center of Qihoo 360 Technology Co. Ltd.: CVE-2016-6762

Additional thanks to thank MengLuo Gou (@idhyt3r) of Bottle Tech, Yong Wang (王勇) (@ThomasKing2014), and Zubin Mithra of Google for their contributions to this security bulletin.

2016-12-01 security level—Vulnerability details

In the sections below, we provide details for each of the security vulnerabilities that apply to the 2016-12-01 level. There is a description of the issue, a severity rationale, and a table with the CVE, associated references, severity, updated Google devices, updated AOSP versions (where applicable), and date reported. When available, we will 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.

Remote code execution vulnerability in CURL/LIBCURL

The table contains security vulnerabilities affecting the CURL and LIBCURL libraries. The most severe issue could enable a man-in-the-middle attacker using a forged certificate to execute arbitrary code within the context of a privileged process. This issue is rated as High due to the attacker needing a forged certificate.

Elevation of privilege vulnerability in libziparchive

An elevation of privilege vulnerability in the libziparchive library could enable a local malicious application to execute arbitrary code within the context of a privileged process. This issue is rated as High because it could be used to gain local access to elevated capabilities, which are not normally accessible to a third-party application.

Denial of service vulnerability in Telephony

A denial of service vulnerability in Telephony could enable a local malicious application to use a specially crafted file to cause a device hang or reboot. This issue is rated as High due to the possibility of local permanent denial of service.

Denial of service vulnerability in Mediaserver

A denial of service vulnerability in Mediaserver could enable an attacker to use a specially crafted file to cause a device hang or reboot. This issue is rated as High due to the possibility of remote denial of service.

* Supported Google devices on Android 7.0 or later that have installed all available updates are not affected by this vulnerability.

Remote Code Execution vulnerability in Framesequence library

A remote code execution vulnerability in the Framesequence library could enable an attacker using a specially crafted file to execute arbitrary code in the context of an unprivileged process. This issue is rated as High due to the possibility of remote code execution in an application that uses the Framesequence library.

Elevation of privilege vulnerability in Smart Lock

An elevation of privilege vulnerability in Smart Lock could enable a local malicious user to access Smart Lock settings without a PIN. This issue is rated as Moderate because it first requires physical access to an unlocked device where Smart Lock was the last settings pane accessed by the user.

* Supported Google devices on Android 7.0 or later that have installed all available updates are not affected by this vulnerability.

Elevation of privilege vulnerability in Framework APIs

An elevation of privilege vulnerability in the Framework API could enable a local malicious application to access system functions beyond its access level. This issue is rated as Moderate because it is a local bypass of restrictions on a constrained process.

Elevation of privilege vulnerability in Telephony

An elevation of privilege vulnerability in Telephony could enable a local malicious application to access system functions beyond its access level. This issue is rated as Moderate because it is a local bypass of restrictions on a constrained process.

Elevation of privilege vulnerability in Wi-Fi

An elevation of privilege vulnerability in Wi-Fi could enable a local malicious application to execute arbitrary code within the context of a privileged process. This issue is rated as Moderate because it first requires compromising a privileged process.

Information disclosure vulnerability in Mediaserver

An information disclosure vulnerability in Mediaserver could enable a local malicious application to access data outside of its permission levels. This issue is rated as Moderate because it could be used to access sensitive data without permission.

Information disclosure vulnerability in Package Manager

An information disclosure vulnerability in Package Manager could enable a local malicious application to bypass operating system protections that isolate application data from other applications. This issue is rated as Moderate because it first requires compromising a privileged process.

2016-12-05 security level—Vulnerability details

In the sections below, we provide details for each of the security vulnerabilities that apply to the 2016-12-05 level. There is a description of the issue, a severity rationale, and a table with the CVE, associated references, severity, updated Google devices, updated AOSP versions (where applicable), and date reported. When available, we will 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.

Elevation of privilege vulnerability in kernel memory subsystem

An elevation of privilege vulnerability in the kernel memory subsystem could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Critical due to the possibility of a local permanent device compromise, which may require reflashing the operating system to repair the device.

Elevation of privilege vulnerability in NVIDIA GPU driver

An elevation of privilege vulnerability in the NVIDIA GPU driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Critical due to the possibility of a local permanent device compromise, which may require reflashing the operating system to repair the device.

* The for this issue is not publicly available. The update is contained in the latest binary drivers for Google devices available from the Google Developer site.

Elevation of privilege vulnerability in kernel

An elevation of privilege vulnerability in the kernel could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Critical due to the possibility of a local permanent device compromise, which may require reflashing the operating system to repair the device.

* Supported Google devices on Android 7.0 or later that have installed all available updates are not affected by this vulnerability.

Elevation of privilege vulnerability in NVIDIA video driver

An elevation of privilege vulnerability in the NVIDIA video driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Critical due to the possibility of a local permanent device compromise, which may require reflashing the operating system to repair the device.

* The for this issue is not publicly available. The update is contained in the latest binary drivers for Google devices available from the Google Developer site.

Elevation of privilege vulnerability in kernel ION driver

An elevation of privilege vulnerability in the kernel ION driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Critical due to the possibility of a local permanent device compromise, which may require reflashing the operating system to repair the device.

Vulnerabilities in Qualcomm components

The following vulnerabilities affects Qualcomm components and is described in further detail in Qualcomm AMSS November 2015 security bulletin.

* The severity rating for these vulnerabilities was determined by the vendor.

** The for this issue is not publicly available. The update is contained in the latest binary drivers for Google devices available from the Google Developer site.

Elevation of privilege vulnerability in kernel file system

An elevation of privilege vulnerability in the kernel file system could enable a local malicious application to bypass operating system protections that isolate application data from other applications. This issue is rated as High because it could be used to gain local access to elevated capabilities, which are not normally accessible to a third-party application.

Elevation of privilege vulnerability in kernel

An elevation of privilege vulnerability in the kernel could enable a local malicious application to to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires exploitation of a separate vulnerability.

Elevation of privilege vulnerability in HTC sound codec driver

An elevation of privilege vulnerability in the HTC sound codec driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.

* The for this issue is not publicly available. The update is contained in the latest binary drivers for Google devices available from the Google Developer site.

Elevation of privilege vulnerability in MediaTek driver

An elevation of privilege vulnerability in the MediaTek driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.

* Supported Google devices on Android 7.0 or later that have installed all available updates are not affected by this vulnerability.

Elevation of privilege vulnerability in Qualcomm media codecs

An elevation of privilege vulnerability in Qualcomm media codecs could enable a local malicious application to execute arbitrary code within the context of a privileged process. This issue is rated as High because it could be used to gain local access to elevated capabilities, which are not normally accessible to a third-party application.

* The for this issue is not publicly available. The update is contained in the latest binary drivers for Google devices available from the Google Developer site.

Elevation of privilege vulnerability in Qualcomm camera driver

An elevation of privilege vulnerability in the Qualcomm camera driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.

Elevation of privilege vulnerability in kernel performance subsystem

An elevation of privilege vulnerability in the kernel performance subsystem could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.

Elevation of privilege vulnerability in MediaTek I2C driver

An elevation of privilege vulnerability in the MediaTek I2C driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.

* Supported Google devices on Android 7.0 or later that have installed all available updates are not affected by this vulnerability.

Elevation of privilege vulnerability in NVIDIA libomx library

An elevation of privilege vulnerability in the NVIDIA libomx library (libnvomx) could enable a local malicious application to execute arbitrary code within the context of a privileged process. This issue is rated as High because it could be used to gain local access to elevated capabilities, which are not normally accessible to a third-party application.

* The for this issue is not publicly available. The update is contained in the latest binary drivers for Google devices available from the Google Developer site.

Elevation of privilege vulnerability in Qualcomm sound driver

An elevation of privilege vulnerability in the Qualcomm sound driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.

Elevation of privilege vulnerability in kernel security subsystem

An elevation of privilege vulnerability in the kernel security subsystem could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.

Elevation of privilege vulnerability in Synaptics touchscreen driver

An elevation of privilege vulnerability in the Synaptics touchscreen driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.

* The for this issue is not publicly available. The update is contained in the latest binary drivers for Google devices available from the Google Developer site.

Elevation of privilege vulnerability in Broadcom Wi-Fi driver

An elevation of privilege vulnerability in the Broadcom Wi-Fi driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.

* Supported Google devices on Android 7.0 or later that have installed all available updates are not affected by this vulnerability.

Information disclosure vulnerability in MediaTek video driver

An information disclosure vulnerability in the MediaTek video driver could enable a local malicious application to access data outside of its permission levels. This issue is rated as High because it could be used to access sensitive data without explicit user permission.

* Supported Google devices on Android 7.0 or later that have installed all available updates are not affected by this vulnerability.

Information disclosure vulnerability in NVIDIA video driver

An information disclosure vulnerability in the NVIDIA video driver could enable a local malicious application to access data outside of its permission levels. This issue is rated as High because it could be used to access sensitive data without explicit user permission.

* The for this issue is not publicly available. The update is contained in the latest binary drivers for Google devices available from the Google Developer site.

Denial of service vulnerability in GPS

A denial of service vulnerability in the Qualcomm GPS component could enable a remote attacker to cause a device hang or reboot. This issue is rated as High due to the possibility of a temporary remote denial of service.

* The for this issue is not publicly available. The update is contained in the latest binary drivers for Google devices available from the Google Developer site.

Denial of service vulnerability in NVIDIA camera driver

A denial of service vulnerability in the NVIDIA camera driver could enable an attacker to cause a local permanent denial of service, which may require reflashing the operating system to repair the device. This issue is rated as High due to the possibility of local permanent denial of service.

* The for this issue is not publicly available. The update is contained in the latest binary drivers for Google devices available from the Google Developer site.

Elevation of privilege vulnerability in kernel networking subsystem

An elevation of privilege vulnerability in the kernel networking subsystem could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Moderate because it first requires compromising a privileged process and current compiler optimizations restrict access to the vulnerable code.

* The for this issue is not publicly available. The update is contained in the latest binary drivers for Google devices available from the Google Developer site.

Information disclosure vulnerability in Qualcomm components

An information disclosure vulnerability in Qualcomm components including the camera driver and video driver could enable a local malicious application to access data outside of its permission levels. This issue is rated as Moderate because it first requires compromising a privileged process.

Information disclosure vulnerability in NVIDIA librm library

An information disclosure vulnerability in the NVIDIA librm library (libnvrm) could enable a local malicious application to access data outside of its permission levels. This issue is rated as Moderate because it could be used to access sensitive data without permission.

* The for this issue is not publicly available. The update is contained in the latest binary drivers for Google devices available from the Google Developer site.

Information disclosure vulnerability in kernel components

An information disclosure vulnerability in kernel components including the ION subsystem, Binder, USB driver and networking subsystem could enable a local malicious application to access data outside of its permission levels. This issue is rated as Moderate because it first requires compromising a privileged process.

* The for this issue is not publicly available. The update is contained in the latest binary drivers for Google devices available from the Google Developer site.

Information disclosure vulnerability in NVIDIA video driver

An information disclosure vulnerability in the NVIDIA video driver could enable a local malicious application to access data outside of its permission levels. This issue is rated as Moderate because it first requires compromising a privileged process.

* The for this issue is not publicly available. The update is contained in the latest binary drivers for Google devices available from the Google Developer site.

Information disclosure vulnerability in Qualcomm sound driver

An information disclosure vulnerability in the Qualcomm sound driver could enable a local malicious application to access data outside of its permission levels. This issue is rated as Moderate because it first requires compromising a privileged process.

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 level, read the instructions on the Pixel and Nexus update schedule.

• Security levels of 2016-12-01 or later address all issues associated with the 2016-12-01 security level.
• Security levels of 2016-12-05 or later address all issues associated with the 2016-12-05 security level and all previous levels.

Device manufacturers that include these updates should set the string level to:

• [ro.build.version.security_]:[2016-12-01]
• [ro.build.version.security_]:[2016-12-05]

2. Why does this bulletin have two security levels?

This bulletin has two security 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 level.

• Devices that use the December 1, 2016 security level must include all issues associated with that security level, as well as fixes for all issues reported in previous security bulletins.
• Devices that use the security level of December 5, 2016 or newer must include all applicable es in this (and previous) security bulletins.

Partners are encouraged to bundle the fixes for all issues they are addressing in a single update.

3. How do I determine which Google devices are affected by each issue?

In the 2016-12-01 and 2016-12-05 security vulnerability details sections, each table has an Updated Google devices column that covers the range of affected Google devices updated for each issue. This column has a few options:

• All Google devices: If an issue affects All and Pixel devices, the table will have "All" in the Updated Google devices column. "All" encapsulates the following supported devices: Nexus 5, Nexus 5X, Nexus 6, Nexus 6P, Nexus 9, Android One, Nexus Player, Pixel C, Pixel, and Pixel XL.
• Some Google devices: If an issue doesn't affect all Google devices, the affected Google devices are listed in the Updated Google devices column.
• No Google devices: If no Google devices running Android 7.0 are affected by the issue, the table will have "None" in the Updated Google devices column.

4. What do the entries in the references column map to?

Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs. These prefixes map as follows:

Revisions

• December 05, 2016: Bulletin published.
• December 07, 2016: Bulletin revised to include AOSP links and updated attribution for CVE-2016-6915, CVE-2016-6916 and CVE-2016-6917.
• December 21, 2016: Corrected typos in CVE-2016-8411 description and Common Questions and Answers.