CVSS2
Attack Vector
NETWORK
Attack Complexity
LOW
Authentication
NONE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:N/AC:L/Au:N/C:C/I:C/A:C
CVSS3
Attack Vector
LOCAL
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
Percentile
91.3%
We have released a security update to Nexus devices through an over-the-air (OTA) update as part of our Android Security Bulletin Monthly Release process. The Nexus firmware images have also been released to the Google Developer site. Builds LMY49H or later and Android M with Security Patch Level of March 01, 2016 or later address these issues. Refer to the Nexus documentation for instructions on how to check the security patch level.
Partners were notified about the issues described in the bulletin on February 1, 2016 or earlier. Where applicable, source code patches for these issues have been released to the Android Open Source Project (AOSP) repository.
The most severe of these issues is a Critical security vulnerability that could enable remote code execution on an affected device through multiple methods such as email, web browsing, and MMS when processing media files. 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 of these newly reported issues. Refer to the 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.
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.
We would like to thank these researchers for their contributions:
In the sections below, we provide details for each of the security vulnerabilities that apply to the 2016-03-01 patch level. There is a description of the issue, a severity rationale, and a table with the CVE, associated bug, severity, affected versions, and date reported. When available, we will link the AOSP change that addressed the issue to the bug ID. When multiple changes relate to a single bug, additional AOSP references are linked to numbers following the bug ID.
During media file and data processing of a specially crafted file, vulnerabilities in mediaserver could allow an attacker to cause memory corruption and remote code execution as the mediaserver process.
The affected functionality is provided as a core part of the operating system, and there are multiple applications that allow it to be reached with remote content, most notably MMS and browser playback of media.
This issue is rated as a Critical severity due to the possibility of remote code execution within the context of the mediaserver service. The mediaserver service has access to audio and video streams as well as access to privileges that third-party apps could not normally access.
CVE | Bugs with AOSP links | Severity | Updated versions | Date reported |
---|---|---|---|---|
CVE-2016-0815 | ANDROID-26365349 | Critical | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1 | Google Internal |
CVE-2016-0816 | ANDROID-25928803 | Critical | 6.0, 6.0.1 | Google Internal |
During media file and data processing of a specially crafted file, vulnerabilities in mediaserver could allow an attacker to cause memory corruption and remote code execution as the mediaserver process.
The affected functionality is provided as a core part of the operating system and there are multiple applications that allow it to be reached with remote content, most notably MMS and browser playback of media.
The issues are rated as Critical severity because they could be used for remote code execution within the context of the mediaserver service. The mediaserver service has access to audio and video streams as well as access to privileges that third-party apps cannot normally access.
CVE | Bug with AOSP links | Severity | Updated versions | Date reported |
---|---|---|---|---|
CVE-2016-1621 | ANDROID-23452792 [2] [3] | Critical | 4.4.4, 5.0.2, 5.1.1, 6.0 | Google Internal |
A vulnerability in Conscrypt could allow a specific type of invalid certificate, issued by an intermediate Certificate Authority (CA), to be incorrectly trusted. This may enable a man-in-the-middle attack. This issue is rated as a Critical severity due to the possibility of an elevation of privilege and remote arbitrary code execution.
CVE | Bug with AOSP links | Severity | Updated versions | Date reported |
---|---|---|---|---|
CVE-2016-0818 | ANDROID-26232830 [2] | Critical | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1 | Google Internal |
An elevation of privilege vulnerability in the Qualcomm performance component could enable a local malicious application to execute arbitrary code in the kernel. This issue is rated as a Critical severity due to the possibility of a local permanent device compromise, and the device could only be repaired by re-flashing the operating system.
CVE | Bug | Severity | Updated versions | Date reported |
---|---|---|---|---|
CVE-2016-0819 | ANDROID-25364034* | Critical | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1 | Oct 29, 2015 |
There is a vulnerability in the MediaTek Wi-Fi kernel driver that could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as a Critical severity due to the possibility of elevation of privilege and arbitrary code execution in the context of the kernel.
CVE | Bug | Severity | Updated versions | Date reported |
---|---|---|---|---|
CVE-2016-0820 | ANDROID-26267358* | Critical | 6.0.1 | Dec 18, 2015 |
An elevation of privilege vulnerability in the Kernel Keyring Component could enable a local malicious application to execute arbitrary code within the kernel. This issue is rated as a Critical severity due to the possibility of a local permanent device compromise and the device could potentially only be repaired by re-flashing the operating system. However, in Android versions 5.0 and above, SELinux rules prevents third-party applications from reaching the affected code.
Note: For reference, the patch in AOSP is available for specific kernel versions: 4.1, 3.18, 3.14, and 3.10.
CVE | Bug | Severity | Updated versions | Date reported |
---|---|---|---|---|
CVE-2016-0728 | ANDROID-26636379 | Critical | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1 | Jan 11, 2016 |
A mitigation bypass vulnerability in the kernel could permit a bypass of security measures in place to increase the difficulty of attackers exploiting the platform. This issue is rated as High severity because it could permit a bypass of security measures in place to increase the difficulty of attackers exploiting the platform.
Note: The update for this issue is located in the Linux upstream.
CVE | Bug | Severity | Updated versions | Date reported |
---|---|---|---|---|
CVE-2016-0821 | ANDROID-26186802 | High | 6.0.1 | Google Internal |
There is an elevation of privilege vulnerability in a MediaTek connectivity kernel driver that could enable a local malicious application to execute arbitrary code within the context of the kernel. Normally a kernel code execution bug like this would be rated critical, but because it requires first compromising the conn_launcher service, it justifies a downgrade to High severity rating.
CVE | Bug | Severity | Updated versions | Date reported |
---|---|---|---|---|
CVE-2016-0822 | ANDROID-25873324* | High | 6.0.1 | Nov 24, 2015 |
An information disclosure vulnerability in the kernel could permit a bypass of security measures in place to increase the difficulty of attackers exploiting the platform. These issues are rated as High severity because they could allow a local bypass of exploit mitigation technologies such as ASLR in a privileged process.
Note: The fix for this issue is located in Linux upstream.
CVE | Bug | Severity | Updated versions | Date reported |
---|---|---|---|---|
CVE-2016-0823 | ANDROID-25739721* | High | 6.0.1 | Google Internal |
An information disclosure vulnerability in libstagefright could permit a bypass of security measures in place to increase the difficulty of attackers exploiting the platform. These issues are rated as High severity because they could also be used to gain elevated capabilities, such as Signature or SignatureOrSystem permissions privileges, which are not accessible to third-party applications.
CVE | Bug with AOSP link | Severity | Updated versions | Date reported |
---|---|---|---|---|
CVE-2016-0824 | ANDROID-25765591 | High | 6.0, 6.0.1 | Nov 18, 2015 |
An information disclosure vulnerability in the Widevine Trusted Application could allow code running in the kernel context to access information in TrustZone secure storage. This issue is rated as High severity because it could be used to gain elevated capabilities, such as Signature or SignatureOrSystem permissions privileges.
CVE | Bug(s) | Severity | Updated versions | Date reported |
---|---|---|---|---|
CVE-2016-0825 | ANDROID-20860039* | High | 6.0.1 | Google Internal |
An elevation of privilege vulnerability in mediaserver could enable a local malicious application to execute arbitrary code within the context of an elevated system application. This issue is rated as High severity because it could be used to gain elevated capabilities, such as Signature or SignatureOrSystem permissions privileges, which are not accessible to a third-party application.
CVE | Bugs with AOSP links | Severity | Updated versions | Date reported |
---|---|---|---|---|
CVE-2016-0826 | ANDROID-26265403 [2] | High | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1 | Dec 17, 2015 |
CVE-2016-0827 | ANDROID-26347509 | High | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1 | Dec 28, 2015 |
An information disclosure vulnerability in mediaserver could permit a bypass of security measures in place to increase the difficulty of attackers exploiting the platform. These issues are rated as High severity because they could also be used to gain elevated capabilities, such as Signature or SignatureOrSystem permissions privileges, which are not accessible to third-party applications.
CVE | Bugs with AOSP links | Severity | Updated versions | Date reported |
---|---|---|---|---|
CVE-2016-0828 | ANDROID-26338113 | High | 5.0.2, 5.1.1, 6.0, 6.0.1 | Dec 27, 2015 |
CVE-2016-0829 | ANDROID-26338109 | High | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1 | Dec 27, 2015 |
A remote denial of service vulnerability in the Bluetooth component could allow a proximal attacker to block access to an affected device. An attacker could cause an overflow of identified Bluetooth devices in the Bluetooth component, which leads to memory corruption and service stop. This is rated as a High severity because it leads to a Denial of Service to the Bluetooth service, which could potentially only be fixed with a flash of the device.
CVE | Bug with AOSP link | Severity | Updated versions | Date reported |
---|---|---|---|---|
CVE-2016-0830 | ANDROID-26071376 | High | 6.0, 6.0.1 | Google Internal |
An information disclosure vulnerability in the Telephony component could allow an application to access sensitive information. This issue is rated Moderate severity because it could be used to improperly access data without permission.
CVE | Bug with AOSP link | Severity | Updated versions | Date reported |
---|---|---|---|---|
CVE-2016-0831 | ANDROID-25778215 | Moderate | 5.0.2, 5.1.1, 6.0, 6.0.1 | Nov 16, 2015 |
A vulnerability in the Setup Wizard could enable an attacker who had physical access to the device to gain access to device settings and perform a manual device reset. This issue is rated as Moderate severity because it could be used to improperly work around the factory reset protection.
CVE | Bug(s) | Severity | Updated versions | Date reported |
---|---|---|---|---|
CVE-2016-0832 | ANDROID-25955042* | Moderate | 5.1.1, 6.0, 6.0.1 | Google Internal |
This section reviews answers to common questions that may occur after reading this bulletin.
1. How do I determine if my device is updated to address these issues?
Builds LMY49H or later and Android 6.0 with Security Patch Level of March 1, 2016 or later address these issues. Refer to the Nexus documentation for instructions on how to check the security patch level. Device manufacturers that include these updates should set the patch string level to: [ro.build.version.security_patch]:[2016-03-01]
CVSS2
Attack Vector
NETWORK
Attack Complexity
LOW
Authentication
NONE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:N/AC:L/Au:N/C:C/I:C/A:C
CVSS3
Attack Vector
LOCAL
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
Percentile
91.3%