Google has released the December 2018 Android Security Bulletin, giving carriers and device makers a fresh set of patches to install.
The December bulletin contains general security patches for some remote and local flaws affecting all Android devices, and also includes a number of updates and fixes specifically targeting Pixel devices.
The update addresses RAM management issues on the Pixel 3 and is said to improve memory performance in certain circumstances, which pertains to issues reported by Pixel 3 users of the phone mismanaging memory for the sake of saving battery power in weird ways, such as randomly killing a music app left running in the background because you launched the camera.
Other fixes affecting Pixel devices include updates from both HTC and Qualcomm for low-level device drivers and bootloaders. Updated Pixel devices will also get camera improvements and improved Android Auto compatibility, Bluetooth patches, and improved notifications when using the Pixel Stand.
Though Google puts out the Android security patches each month, the job of actually getting the fixes to end users falls on the telcos and/or device manufacturers themselves. Those partners vary in their ability to release the patches in a timely fashion
The December bulletin has two security patch levels to provide Android partners with the flexibility to more quickly fix a subset of vulnerabilities that are similar across all Android devices.
- 01-12-2018: Partial security patch level string. This security patch level string indicates that all issues associated with 01-12-2018 (and all previous security patch level strings) are addressed.
- 05-12-2018: Complete security patch level string. This security patch level address all issues associated with the 05-12-2018 security patch level and all previous patch levels.
The most severe of these issues is a critical security vulnerability in Media framework that could enable a remote attacker using a specially crafted file to execute arbitrary code within the context of a privileged process. 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 turned off for development purposes or if successfully bypassed.
Alongside the bulletin, Google 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 patch levels of December 5, 2018 or later address all of these issues.
The tables below contains a list of security vulnerabilities, the Common Vulnerability and Exposures ID (CVE), the assessed severity, and whether or not Google devices are affected. 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.
Android and Google Service Mitigation’s
This is a summary of the mitigation’s provided by the Android security platform and service protections such as Google Play Protect. 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. All users are encouraged to update to the latest version of Android where possible.
- The Android security team actively monitors for abuse through Google Play Protect and warns users about Potentially Harmful Applications. Google Play Protect is enabled by default on devices with Google Mobile Services, and is especially important for users who install apps from outside of Google Play.
Terminology
You will find different types of vulnerabilities listed. Possible types include:
- RCE—Remote code execution
- EoP—Elevation of privilege
- ID—Information disclosure
- DoS—Denial of service
01-12-2018 security patch level—Vulnerability details
Framework
The most severe vulnerability in this section could enable a local malicious application to execute arbitrary code within the context of a privileged process.
| CVE | References | Type | Severity | Updated AOSP versions |
|---|---|---|---|---|
| CVE-2018-9547 | A-114223584 | EoP | High | 8.1, 9 |
| CVE-2018-9548 | A-112555574 | ID | High | 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9 |
Media framework
The most severe vulnerability in this section could enable a remote attacker using a specially crafted file to execute arbitrary code within the context of a privileged process.
| CVE | References | Type | Severity | Updated AOSP versions |
|---|---|---|---|---|
| CVE-2018-9549 | A-112160868 | RCE | Critical | 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9 |
| CVE-2018-9550 | A-112660981 | RCE | Critical | 9 |
| CVE-2018-9551 | A-112891548 | RCE | Critical | 9 |
| CVE-2018-9552 | A-113260892 | ID | Critical | 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9 |
| CVE-2018-9553 | A-116615297 | RCE | High | 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9 |
| CVE-2018-9538 | A-112181526 | EoP | High | 8.1, 9 |
| CVE-2018-9554 | A-114770654 | ID | High | 7.0, 7.1.1, 7.1.2, 8.0, 8.1 |
System
The most severe vulnerability in this section could enable a remote attacker using a specially crafted transmission to execute arbitrary code within the context of a privileged process.
| CVE | References | Type | Severity | Updated AOSP versions |
|---|---|---|---|---|
| CVE-2018-9555 | A-112321180 | RCE | Critical | 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9 |
| CVE-2018-9556 | A-113118184 | RCE | Critical | 9 |
| CVE-2018-9557 | A-35385357 | EoP | High | 7.0, 7.1.1, 7.1.2 |
| CVE-2018-9558 | A-112161557 | EoP | High | 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9 |
| CVE-2018-9559 | A-112731440 | EoP | High | 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9 |
| CVE-2018-9560 | A-79946737 | EoP | High | 9 |
| CVE-2018-9562 | A-113164621 | ID | High | 9 |
| CVE-2018-9566 | A-74249842 | ID | High | 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9 |
05-12-2018 security patch level—Vulnerability details
System
The most severe vulnerability in this section could lead to remote information disclosure with no additional execution privileges needed.
| CVE | References | Type | Severity | Component |
|---|---|---|---|---|
| CVE-2018-9565 | A-16680558 | ID | High | OMA-DM |
HTC components
The most severe vulnerability in this section could enable a local attacker to bypass user interaction requirements in order to gain access to additional permissions.
| CVE | References | Type | Severity | Component |
|---|---|---|---|---|
| CVE-2018-9567 | A-65543936 | EoP | High | Bootloader |
Kernel components
The most severe vulnerability in this section could enable a local attacker to execute arbitrary code within the context of a privileged process.
| CVE | References | Type | Severity | Component |
|---|---|---|---|---|
| CVE-2018-10840 | A-116406508 Upstream kernel |
EoP | High | ext4 filesystem |
| CVE-2018-9568 | A-113509306 Upstream kernel |
EoP | High | network |
Qualcomm components
These vulnerabilities affect Qualcomm components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm.
| CVE | References | Type | Severity | Component |
|---|---|---|---|---|
| CVE-2018-11960 | A-114042002 QC-CR#2264832 |
N/A | High | HWEngines |
| CVE-2018-11961 | A-114040881 QC-CR#2261813 |
N/A | High | GPS_AP_LINUX |
| CVE-2018-11963 | A-114041685 QC-CR#2220770 |
N/A | High | Automotive Multimedia |
Qualcomm closed-source components
These vulnerabilities affect Qualcomm components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm.
| CVE | References | Type | Severity | Component |
|---|---|---|---|---|
| CVE-2017-8248 | A-78135902 | N/A | Critical | Closed-source component |
| CVE-2017-11004 | A-66913713 | N/A | Critical | Closed-source component |
| CVE-2017-18141 | A-67712316 | N/A | Critical | Closed-source component |
| CVE-2018-5913 | A-79419833 | N/A | Critical | Closed-source component |
| CVE-2018-11279 | A-109678200 | N/A | Critical | Closed-source component |
| CVE-2017-18319 | A-78284753 | N/A | High | Closed-source component |
| CVE-2017-18321 | A-78283451 | N/A | High | Closed-source component |
| CVE-2017-18322 | A-78285196 | N/A | High | Closed-source component |
| CVE-2017-18323 | A-78284194 | N/A | High | Closed-source component |
| CVE-2017-18324 | A-78284517 | N/A | High | Closed-source component |
| CVE-2017-18327 | A-78240177 | N/A | High | Closed-source component |
| CVE-2017-18331 | A-78239686 | N/A | High | Closed-source component |
| CVE-2017-18332 | A-78284545 | N/A | High | Closed-source component |
| CVE-2017-18160 | A-109660689 | N/A | High | Closed-source component |
| CVE-2017-18326 | A-78240324 | N/A | High | Closed-source component |
| CVE-2017-8276 | A-68141338 | N/A | High | Closed-source component |
| CVE-2017-18328 | A-78286046 | N/A | High | Closed-source component |
| CVE-2017-18329 | A-73539037 | N/A | High | Closed-source component |
| CVE-2017-18330 | A-73539235 | N/A | High | Closed-source component |
| CVE-2018-3595 | A-71501115 | N/A | High | Closed-source component |
| CVE-2017-18320 | A-33757308 | N/A | High | Closed-source component |
| CVE-2018-11999 | A-74236942 | N/A | High | Closed-source component |
| CVE-2018-5867 | A-77485184 | N/A | High | Closed-source component |
| CVE-2018-5868 | A-77484529 | N/A | High | Closed-source component |
| CVE-2018-5869 | A-33385206 | N/A | High | Closed-source component |
| CVE-2017-5754 | A-79419639 | N/A | High | Closed-source component |
| CVE-2018-5915 | A-79420511 | N/A | High | Closed-source component |
| CVE-2018-11267 | A-109678338 | N/A | High | Closed-source component |
| CVE-2018-11922 | A-112279564 | N/A | High | Closed-source component |
Full details of the December 2018 Android Security Bulletin are available here.
