{"androidsecurity": [{"lastseen": "2023-10-01T16:53:13", "description": "The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Security patch levels of 2020-03-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](<https://support.google.com/pixelphone/answer/4457705>).\n\nAndroid 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.\n\nThe most severe of these issues is a critical security vulnerability in the 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.\n\nRefer 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.\n\n**Note**: Information on the latest over-the-air update (OTA) and firmware images for Google devices is available in the March 2020 Pixel Update Bulletin. \n\n## Android and Google service mitigations\n\nThis is a summary of the mitigations provided by the Android security platform and service protections such as [Google Play Protect](<https://developers.google.com/android/play-protect/>). These capabilities reduce the likelihood that security vulnerabilities could be successfully exploited on Android.\n\n * 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.\n * The Android security team actively monitors for abuse through [Google Play Protect](<https://developers.google.com/android/play-protect/>) and warns users about [Potentially Harmful Applications](<https://developers.google.com/android/play-protect/potentially-harmful-applications>). Google Play Protect is enabled by default on devices with [Google Mobile Services](<http://www.android.com/gms>), and is especially important for users who install apps from outside of Google Play.\n\n## 2020-03-01 security patch level vulnerability details\n\nIn the sections below, we provide details for each of the security vulnerabilities that apply to the 2020-03-01 patch level. Vulnerabilities are grouped under the component that they affect. Issues are described in the tables below and include CVE ID, 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, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID. Devices with Android 10 and later may receive security updates as well as [Google Play system updates](<https://support.google.com/android/answer/7680439?hl=en>).\n\n### Framework\n\nThe vulnerability in this section could enable a local malicious application to bypass operating system protections that isolate application data from other applications.\n\nCVE | References | Type | Severity | Updated AOSP versions \n---|---|---|---|--- \nCVE-2020-0031 | [A-141703197](<https://android.googlesource.com/platform/cts/+/4534471b6c16a5676b85b76452d287667175c1ee>) [[2](<https://android.googlesource.com/platform/frameworks/base/+/514271fd61e4219e99a8e5306cdc7b80c3c1c445>)] | ID | High | 10 \n \n### Media framework\n\nThe 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.\n\nCVE | References | Type | Severity | Updated AOSP versions \n---|---|---|---|--- \nCVE-2020-0032 | [A-145364230](<https://android.googlesource.com/platform/external/libavc/+/ffcf2a87d66f935210ebd011eed474514d086b40>) | RCE | Critical | 8.0, 8.1, 9, 10 \nCVE-2020-0033 | [A-144351324](<https://android.googlesource.com/platform/hardware/interfaces/+/d79abbb0d359dd037e6d0b4cc022fd26cea3ebaa>) | EoP | High | 8.0, 8.1, 9, 10 \nCVE-2020-0034 | [A-62458770](<https://android.googlesource.com/platform/external/libvpx/+/30d0c20d0d04151530de62df3937de27c4f204fd>) | ID | High | 8.0, 8.1 \n \n### System\n\nThe most severe vulnerability in this section could enable a local malicious application to bypass user interaction requirements in order to gain access to additional permissions.\n\nCVE | References | Type | Severity | Updated AOSP versions \n---|---|---|---|--- \nCVE-2020-0036 | [A-144679405](<https://android.googlesource.com/platform/frameworks/base/+/9352cb24b1afaec657faeffdb0d40ed96d4d912b>) | EoP | High | 8.0, 8.1, 9, 10 \nCVE-2020-0035 | [A-140622024](<https://android.googlesource.com/platform/packages/providers/TelephonyProvider/+/099c68c403c470aaafd3a0f7d4bdf69c873d4740>) | ID | High | 8.0, 8.1, 9 \nCVE-2020-0029 | [A-140065828](<https://android.googlesource.com/platform/frameworks/opt/net/wifi/+/2cda452b868328c4600a3d75759968c246cb47c8>) | ID | High | 10 \nCVE-2020-0037 | [A-143106535](<https://android.googlesource.com/platform/system/nfc/+/712dcda25084434ffd3e1e0df6c0f7e65441b7f1>) | ID | High | 8.0, 8.1, 9, 10 \nCVE-2020-0038 | [A-143109193](<https://android.googlesource.com/platform/system/nfc/+/712dcda25084434ffd3e1e0df6c0f7e65441b7f1>) | ID | High | 8.0, 8.1, 9, 10 \nCVE-2020-0039 | [A-143155861](<https://android.googlesource.com/platform/system/nfc/+/712dcda25084434ffd3e1e0df6c0f7e65441b7f1>) | ID | High | 8.0, 8.1, 9, 10 \n \n### Google Play system updates\n\nThe following issue is included in Project Mainline components.\n\nComponent | CVE \n---|--- \nMedia codecs | CVE-2020-0032 \n \n## 2020-03-05 security patch level vulnerability details\n\nIn the sections below, we provide details for each of the security vulnerabilities that apply to the 2020-03-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.\n\n### Kernel components\n\nThe most severe vulnerability in this section could enable a local attacker using a specially crafted USB device to execute arbitrary code within the context of a privileged process.\n\nCVE | References | Type | Severity | Component \n---|---|---|---|--- \nCVE-2019-19527 | A-146257915 [Upstream kernel](<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d4472d7bec39917b54e4e80245784ea5d60ce49>) [[2](<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9c09b214f30e3c11f9b0b03f89442df03643794d>)] | EoP | High | USB \nCVE-2019-19537 | A-146258055 [Upstream kernel](<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=303911cfc5b95d33687d9046133ff184cf5043ff>) | EoP | High | USB \nCVE-2019-15239 | A-143009752 [Upstream kernel](<https://android.googlesource.com/kernel/common/+/3ed1460d6b17326093eb657afa89a7274e444a32>) | EoP | High | Networking \nCVE-2020-0041 | A-145988638 [Upstream kernel](<https://lore.kernel.org/lkml/20191213202531.55010-1-tkjos@google.com/>) | EoP | High | Binder \n \n### FPC components\n\nThe most severe vulnerability in this section could enable a local malicious application to bypass user interaction requirements in order to gain access to additional permissions.\n\nCVE | References | Type | Severity | Component \n---|---|---|---|--- \nCVE-2020-0010 | A-137014293* | EoP | High | FPC Fingerprint TEE \nCVE-2020-0011 | A-137648045* | EoP | High | FPC Fingerprint TEE \nCVE-2020-0012 | A-137648844* | EoP | High | FPC Fingerprint TEE \nCVE-2020-0042 | A-137649599* | ID | Moderate | FPC Fingerprint TEE \nCVE-2020-0043 | A-137650218* | ID | Moderate | FPC Fingerprint TEE \nCVE-2020-0044 | A-137650219* | ID | Moderate | FPC Fingerprint TEE \n \n### MediaTek components\n\nCVE | References | Type | Severity | Component \n---|---|---|---|--- \nCVE-2020-0069 | A-147882143* M-ALPS04356754 | EoP | High | System \n \n### Qualcomm components\n\nThese 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.\n\nCVE | References | Type | Severity | Component \n---|---|---|---|--- \nCVE-2019-14079 | A-138848422 [ QC-CR#2521001](<https://source.codeaurora.org/quic/la/kernel/msm-4.9/commit/?id=d33730844c128e688a8e1e7c354a6efd7bff1bfe>) | N/A | High | USB \nCVE-2018-11838 | A-145545090 [QC-CR#221457](<https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=d98aa07b53021e269afa337e89408418103367be>) [[2](<https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=815cf7b4de9bfe7ed77a04db5c3462d5a29b8e43>)] | N/A | High | WLAN \nCVE-2019-10526 | A-145544085 [QC-CR#2232526](<https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=f5e23c59116af3c7b9597c8aebcaeeb9935f1b96>) [QC-CR#2541970](<https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=f7c43c43192396a06b2b12b40934c9e5c79c9911>) | N/A | High | WLAN \nCVE-2019-10569 | A-145545820 [QC-CR#2315791](<https://source.codeaurora.org/quic/la/platform/hardware/qcom/audio/commit/?id=bbf4497352958dd27036503a43cd8a031e7eb9b1>) | N/A | High | Audio \nCVE-2019-14029 | A-145546793 [QC-CR#2528795](<https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=a8dfad11eb0f3368b517c260d0fe98c84d30ccf4>) | N/A | High | Graphics \nCVE-2019-14032 | A-145546652 [QC-CR#2537311](<https://source.codeaurora.org/quic/la/platform/vendor/opensource/audio-kernel/commit/?id=5ee3d202971888366b6d734de2f92f37cb90656e>) | N/A | High | Audio \nCVE-2019-14068 | A-145546435 [QC-CR#2507653](<https://source.codeaurora.org/quic/la/platform/vendor/opensource/audio-kernel/commit/?id=0274b6d95e23a112fc75ca44f0634632885852fc>) [[2](<https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=66b26c141c4ecaa3c4e0d4dba53a4421550a329c>)] | N/A | High | Audio \nCVE-2019-14072 | A-145545251 [QC-CR#2509391](<https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=1819c4b207f7bcdfff75fff5a629f8766c296fbd>) | N/A | High | Graphics \n \n### Qualcomm closed-source components\n\nThese vulnerabilities affect Qualcomm closed-source 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.\n\nCVE | References | Type | Severity | Component \n---|---|---|---|--- \nCVE-2019-2317 | A-134436812* | N/A | Critical | Closed-source component \nCVE-2019-10586 | A-140423909* | N/A | Critical | Closed-source component \nCVE-2019-10587 | A-140423816* | N/A | Critical | Closed-source component \nCVE-2019-10593 | A-140424165* | N/A | Critical | Closed-source component \nCVE-2019-10594 | A-140424564* | N/A | Critical | Closed-source component \nCVE-2019-10612 | A-140423161* | N/A | Critical | Closed-source component \nCVE-2019-14031 | A-142271912* | N/A | Critical | Closed-source component \nCVE-2019-14045 | A-140973418* | N/A | Critical | Closed-source component \nCVE-2019-14071 | A-145545489* | N/A | Critical | Closed-source component \nCVE-2019-14083 | A-140973259* | N/A | Critical | Closed-source component \nCVE-2019-14086 | A-140973417* | N/A | Critical | Closed-source component \nCVE-2019-14030 | A-145546515* | N/A | Critical | Closed-source component \nCVE-2019-14097 | A-145546003* | N/A | Critical | Closed-source component \nCVE-2019-14098 | A-145546314* | N/A | Critical | Closed-source component \nCVE-2019-10546 | A-145545250* | N/A | Critical | Closed-source component \nCVE-2019-14095 | A-142843397* | N/A | Critical | Closed-source component \nCVE-2018-11970 | A-114042111* | N/A | High | Closed-source component \nCVE-2019-10603 | A-140424074* | N/A | High | Closed-source component \nCVE-2019-10616 | A-140423338* | N/A | High | Closed-source component \nCVE-2019-10549 | A-140423162* | N/A | High | Closed-source component \nCVE-2019-10550 | A-140423702* | N/A | High | Closed-source component \nCVE-2019-10552 | A-140423817* | N/A | High | Closed-source component \nCVE-2019-10553 | A-140423081* | N/A | High | Closed-source component \nCVE-2019-10554 | A-140424012* | N/A | High | Closed-source component \nCVE-2019-10577 | A-140424166* | N/A | High | Closed-source component \nCVE-2019-14026 | A-142271986* | N/A | High | Closed-source component \nCVE-2019-14027 | A-142271756* | N/A | High | Closed-source component \nCVE-2019-14028 | A-142271831* | N/A | High | Closed-source component \nCVE-2019-2300 | A-142271659* | N/A | High | Closed-source component \nCVE-2019-2311 | A-142271967* | N/A | High | Closed-source component \nCVE-2019-14050 | A-143902706* | N/A | High | Closed-source component \nCVE-2019-14081 | A-143902882* | N/A | High | Closed-source component \nCVE-2019-14082 | A-140974589* | N/A | High | Closed-source component \nCVE-2019-14085 | A-143902807* | N/A | High | Closed-source component \nCVE-2019-14048 | A-145545282* | N/A | High | Closed-source component \nCVE-2019-14061 | A-145545758* | N/A | High | Closed-source component \nCVE-2019-10604 | A-145545725* | N/A | High | Closed-source component \nCVE-2019-10591 | A-145545283* | N/A | High | Closed-source component \nCVE-2019-14000 | A-145546434* | N/A | High | Closed-source component \nCVE-2019-14015 | A-145545650* | N/A | High | Closed-source component \n \n## Common questions and answers\n\nThis section answers common questions that may occur after reading this bulletin.\n\n**1\\. How do I determine if my device is updated to address these issues?**\n\nTo learn how to check a device's security patch level, see [Check and update your Android version](<https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices>).\n\n * Security patch levels of 2020-03-01 or later address all issues associated with the 2020-03-01 security patch level.\n * Security patch levels of 2020-03-05 or later address all issues associated with the 2020-03-05 security patch level and all previous patch levels.\n\nDevice manufacturers that include these updates should set the patch string level to:\n\n * [ro.build.version.security_patch]:[2020-03-01]\n * [ro.build.version.security_patch]:[2020-03-05]\n\nFor some devices on Android 10 or later, the Google Play system update will have a date string that matches the 2020-03-01 security patch level. Please see [this article](<https://support.google.com/android/answer/7680439?hl=en>) for more details on how to install security updates.\n\n**2\\. Why does this bulletin have two security patch levels?**\n\nThis 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.\n\n * Devices that use the 2020-03-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.\n * Devices that use the security patch level of 2020-03-05 or newer must include all applicable patches in this (and previous) security bulletins.\n\nPartners are encouraged to bundle the fixes for all issues they are addressing in a single update.\n\n**3\\. What do the entries in the _Type_ column mean?**\n\nEntries in the _Type_ column of the vulnerability details table reference the classification of the security vulnerability.\n\nAbbreviation | Definition \n---|--- \nRCE | Remote code execution \nEoP | Elevation of privilege \nID | Information disclosure \nDoS | Denial of service \nN/A | Classification not available \n \n**4\\. What do the entries in the _References_ column mean?**\n\nEntries under the _References_ column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.\n\nPrefix | Reference \n---|--- \nA- | Android bug ID \nQC- | Qualcomm reference number \nM- | MediaTek reference number \nN- | NVIDIA reference number \nB- | Broadcom reference number \n \n**5\\. What does an * next to the Android bug ID in the _References_ column mean?**\n\nIssues that are not publicly available have an * 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](<https://developers.google.com/android/drivers>).\n\n**6\\. Why are security vulnerabilities split between this bulletin and device&hairsp;/&hairsp;partner security bulletins, such as the Pixel bulletin?**\n\nSecurity 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&hairsp;/&hairsp;partner security bulletins are not required for declaring a security patch level. Android device and chipset manufacturers may also publish security vulnerability details specific to their products, such as Google, [Huawei](<https://consumer.huawei.com/en/support/bulletin/>), [LGE](<https://lgsecurity.lge.com/security_updates_mobile.html>), [Motorola](<https://motorola-global-portal.custhelp.com/app/software-security-page/g_id/6806>), [Nokia](<https://www.nokia.com/phones/en_int/security-updates>), or [Samsung](<https://security.samsungmobile.com/securityUpdate.smsb>). \n\n## Versions\n\nVersion | Date | Notes \n---|---|--- \n1.0 | March 2, 2020 | Bulletin published \n1.1 | March 3, 2020 | Bulletin revised to include AOSP links \n1.2 | March 9, 2020 | Updated issue list\n", "cvss3": {"exploitabilityScore": 3.9, "cvssV3": {"baseSeverity": "CRITICAL", "confidentialityImpact": "HIGH", "attackComplexity": "LOW", "scope": "UNCHANGED", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "baseScore": 9.8, "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "version": "3.1", "userInteraction": "NONE"}, "impactScore": 5.9}, "published": "2020-03-02T00:00:00", "type": "androidsecurity", "title": "Android Security Bulletin\u2014March 2020", "bulletinFamily": "software", "cvss2": {"severity": "HIGH", "exploitabilityScore": 10.0, "obtainAllPrivilege": false, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "LOW", "confidentialityImpact": "COMPLETE", "availabilityImpact": "COMPLETE", "integrityImpact": "COMPLETE", "baseScore": 10.0, "vectorString": "AV:N/AC:L/Au:N/C:C/I:C/A:C", "version": "2.0", "accessVector": "NETWORK", "authentication": "NONE"}, "impactScore": 10.0, "acInsufInfo": false, "obtainUserPrivilege": false}, "cvelist": ["CVE-2018-11838", "CVE-2018-11970", "CVE-2019-10526", "CVE-2019-10546", "CVE-2019-10549", "CVE-2019-10550", "CVE-2019-10552", "CVE-2019-10553", "CVE-2019-10554", "CVE-2019-10569", "CVE-2019-10577", "CVE-2019-10586", "CVE-2019-10587", "CVE-2019-10591", "CVE-2019-10593", "CVE-2019-10594", "CVE-2019-10603", "CVE-2019-10604", "CVE-2019-10612", "CVE-2019-10616", "CVE-2019-14000", "CVE-2019-14015", "CVE-2019-14026", "CVE-2019-14027", "CVE-2019-14028", "CVE-2019-14029", "CVE-2019-14030", "CVE-2019-14031", "CVE-2019-14032", "CVE-2019-14045", "CVE-2019-14048", "CVE-2019-14050", "CVE-2019-14061", "CVE-2019-14068", "CVE-2019-14071", "CVE-2019-14072", "CVE-2019-14079", "CVE-2019-14081", "CVE-2019-14082", "CVE-2019-14083", "CVE-2019-14085", "CVE-2019-14086", "CVE-2019-14095", "CVE-2019-14097", "CVE-2019-14098", "CVE-2019-15239", "CVE-2019-19527", "CVE-2019-19537", "CVE-2019-2300", "CVE-2019-2311", "CVE-2019-2317", "CVE-2020-0010", "CVE-2020-0011", "CVE-2020-0012", "CVE-2020-0029", "CVE-2020-0031", "CVE-2020-0032", "CVE-2020-0033", "CVE-2020-0034", "CVE-2020-0035", "CVE-2020-0036", "CVE-2020-0037", "CVE-2020-0038", "CVE-2020-0039", "CVE-2020-0041", "CVE-2020-0042", "CVE-2020-0043", "CVE-2020-0044", "CVE-2020-0069"], "modified": "2020-03-09T00:00:00", "id": "ANDROID:2020-03-01", "href": "https://source.android.com/docs/security/bulletin/2020-03-01", "cvss": {"score": 10.0, "vector": "AV:N/AC:L/Au:N/C:C/I:C/A:C"}}]}
CVE-2019-14029
