Google is committed to advancing racial equity for Black communities. See how.

Published February 4, 2019

The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Security patch levels of 2019-02-05 or later address all of these issues. To learn how to check a device's security patch level, see Check and update your Android version.

Android partners are notified of all issues at least a month before publication. Source code patches 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 patches outside of AOSP.

The most severe of these issues is a critical security vulnerability in Framework that could allow a remote attacker using a specially crafted PNG 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.

We have had no reports of active customer exploitation or abuse of these newly reported issues. Refer to the Android and Google Play Protect mitigations section for details on the Android security platform protections and Google Play Protect, which improve the security of the Android platform.

Note: Information on the latest over-the-air update (OTA) and firmware images for Google devices is available in the February 2019 Pixel Update Bulletin.

Android and Google service mitigations

This is a summary of the mitigations 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. We encourage all users 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.

2019-02-01 security patch level vulnerability details

In the sections below, we provide details for each of the security vulnerabilities that apply to the 2019-02-01 patch level. Vulnerabilities are grouped under the component they affect. There is a description of the issue and a table with the CVE, associated references, type of vulnerability, severity, and updated AOSP versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, such as the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.

Framework

The most severe vulnerability in this section could enable a remote attacker using a specially crafted PNG file to execute arbitrary code within the context of a privileged process.

CVE References Type Severity Updated AOSP versions CVE-2019-1986 A-117838472 [2] RCE Critical 9 CVE-2019-1987 A-118143775 [2] RCE Critical 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9 CVE-2019-1988 A-118372692 RCE Critical 8.0, 8.1, 9

Library

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 an unprivileged process.

CVE References Type Severity Updated AOSP versions CVE-2017-17760 A-78029030* RCE High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9 CVE-2018-5268 A-78029634* RCE High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9 CVE-2018-5269 A-78029727* RCE High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9 CVE-2017-18009 A-78026242* ID Moderate 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

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-2019-1991 A-110166268 RCE Critical 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9 CVE-2019-1992 A-116222069 RCE Critical 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9 CVE-2019-1993 A-119819889 EoP High 8.0, 8.1, 9 CVE-2019-1994 A-117770924 EoP High 8.0, 8.1, 9 CVE-2019-1995 A-32589229 [2] ID High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9 CVE-2019-1996 A-111451066 ID High 8.0, 8.1, 9 CVE-2019-1997 A-117508900 ID High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9 CVE-2019-1998 A-116055338 [2] DoS High 9

2019-02-05 security patch level vulnerability details

In the sections below, we provide details for each of the security vulnerabilities that apply to the 2019-02-05 patch level. Vulnerabilities are grouped under the component they affect and include details such as the CVE, associated references, type of vulnerability, severity, component (where applicable), and updated AOSP versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, such as the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.

Kernel components

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 Component CVE-2018-10879 A-116406063

Upstream kernel EoP High ext4 filesystem CVE-2019-1999 A-120025196* EoP High Binder driver CVE-2019-2000 A-120025789* EoP High Binder driver CVE-2019-2001 A-117422211* ID High iomem

NVIDIA components

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 Component CVE-2018-6271 A-80198474* RCE Critical libnvomx CVE-2018-6267 A-70857947* EoP High libnvomx CVE-2018-6268 A-80433161* EoP High libnvomx CVE-2016-6684 A-117423758* ID High kernel log

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-11262 A-76424945

QC-CR#2221192 N/A Critical bootloader CVE-2018-11280 A-109741776

QC-CR#2185061 N/A High Modem CVE-2018-11275 A-74409078

QC-CR#2221256 [2] N/A High Bootloader CVE-2018-13900 A-119052051

QC-CR#2287499 N/A High Modem CVE-2018-13905 A-119052050

QC-CR#2225202 N/A High Graphics

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-2018-11289 A-109678453* N/A Critical Closed-source component CVE-2018-11820 A-111089815* N/A Critical Closed-source component CVE-2018-11938 A-112279482* N/A Critical Closed-source component CVE-2018-11945 A-112278875* N/A Critical Closed-source component CVE-2018-11268 A-109678259* N/A High Closed-source component CVE-2018-11845 A-111088838* N/A High Closed-source component CVE-2018-11864 A-111092944* N/A High Closed-source component CVE-2018-11921 A-112278972* N/A High Closed-source component CVE-2018-11931 A-112279521* N/A High Closed-source component CVE-2018-11932 A-112279426* N/A High Closed-source component CVE-2018-11935 A-112279483* N/A High Closed-source component CVE-2018-11948 A-112279144* N/A High Closed-source component CVE-2018-5839 A-112279544* N/A High Closed-source component CVE-2018-13904 A-119050566* N/A High Closed-source component

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 patch level, see Check and update your Android version.

Security patch levels of 2019-02-01 or later address all issues associated with the 2019-02-01 security patch level.

Security patch levels of 2019-02-05 or later address all issues associated with the 2019-02-05 security patch level and all previous patch levels.

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

[ro.build.version.security_patch]:[2019-02-01]

[ro.build.version.security_patch]:[2019-02-05]

2. Why does this bulletin have two security patch levels?

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

Devices that use the 2019-02-01 security patch level must include all issues associated with that security patch level, as well as fixes for all issues reported in previous security bulletins.

Devices that use the security patch level of 2019-02-05 or newer must include all applicable patches in this (and previous) security bulletins.

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

3. 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

4. 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

5. 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 Pixel devices available from the Google Developer site.

6. Why are security vulnerabilities split between this bulletin and device / partner security bulletins, such as the Pixel bulletin?

Security vulnerabilities that are documented in this security bulletin are required to declare the latest security patch level on Android devices. Additional security vulnerabilities that are documented in the device / partner security bulletins are not required for declaring a security patch level. Android device and chipset manufacturers are encouraged to document the presence of other fixes on their devices through their own security websites, such as the Samsung, LGE, or Pixel security bulletins.

Versions