An elevation of privilege vulnerability in libstagefright in Mediaserver 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. Product: Android. Versions: 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1. Android ID: A-34749392.
{"ubuntucve": [{"lastseen": "2022-08-04T14:01:49", "description": "An elevation of privilege vulnerability in libstagefright in Mediaserver\ncould enable a local malicious application to execute arbitrary code within\nthe context of a privileged process. This issue is rated as High because it\ncould be used to gain local access to elevated capabilities, which are not\nnormally accessible to a third-party application. Product: Android.\nVersions: 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1. Android ID:\nA-34749392.", "cvss3": {"exploitabilityScore": 1.8, "cvssV3": {"baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "attackComplexity": "LOW", "scope": "UNCHANGED", "attackVector": "LOCAL", "availabilityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "baseScore": 7.8, "vectorString": "CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "version": "3.0", "userInteraction": "REQUIRED"}, "impactScore": 5.9}, "published": "2017-05-12T00:00:00", "type": "ubuntucve", "title": "CVE-2017-0596", "bulletinFamily": "info", "cvss2": {"severity": "HIGH", "exploitabilityScore": 8.6, "obtainAllPrivilege": false, "userInteractionRequired": true, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "MEDIUM", "confidentialityImpact": "COMPLETE", "availabilityImpact": "COMPLETE", "integrityImpact": "COMPLETE", "baseScore": 9.3, "vectorString": "AV:N/AC:M/Au:N/C:C/I:C/A:C", "version": "2.0", "accessVector": "NETWORK", "authentication": "NONE"}, "impactScore": 10.0, "obtainUserPrivilege": false}, "cvelist": ["CVE-2017-0596"], "modified": "2017-05-12T00:00:00", "id": "UB:CVE-2017-0596", "href": "https://ubuntu.com/security/CVE-2017-0596", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}}], "androidsecurity": [{"lastseen": "2022-08-15T18:03:41", "description": "The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Alongside the bulletin, we have released a security update to Nexus devices through an over-the-air (OTA) update. The Google device firmware images have also been released to the [Google Developer site](<https://developers.google.com/android/nexus/images>). Security patch levels of May 05, 2017 or later address all of these issues. Refer to the [Pixel and Nexus update schedule](<https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices>) to learn how to check a device's security patch level.\n\nPartners were notified of the issues described in the bulletin on April 03, 2017 or earlier. 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 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.\n\nWe 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](<https://developer.android.com/training/safetynet/index.html>), which improve the security of the Android platform.\n\nWe encourage all customers to accept these updates to their devices.\n\n## Announcements\n\n * This bulletin has two security patch 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: \n * **2017-05-01**: Partial security patch level string. This security patch level string indicates that all issues associated with 2017-05-01 (and all previous security patch level strings) are addressed.\n * **2017-05-05**: Complete security patch level string. This security patch level string indicates that all issues associated with 2017-05-01 and 2017-05-05 (and all previous security patch level strings) are addressed.\n * Supported Google devices will receive a single OTA update with the May 05, 2017 security patch level.\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 SafetyNet. 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 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](<http://www.android.com/gms>) 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\u2014no 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.\n * As appropriate, Google Hangouts and Messenger applications do not automatically pass media to processes such as Mediaserver.\n\n## Acknowledgements\n\nWe would like to thank these researchers for their contributions:\n\n * ADlab of Venustech: CVE-2017-0630\n * Di Shen ([@returnsme](<https://twitter.com/returnsme>)) of KeenLab ([@keen_lab](<https://twitter.com/keen_lab>)), Tencent: CVE-2016-10287\n * Ecular Xu (\u5f90\u5065) of Trend Micro: CVE-2017-0599, CVE-2017-0635\n * En He ([@heeeeen4x](<https://twitter.com/heeeeen4x>)) and Bo Liu of [MS509Team](<http://www.ms509.com>): CVE-2017-0601\n * Ethan Yonker of [Team Win Recovery Project](<https://twrp.me/>): CVE-2017-0493\n * Gengjia Chen ([@chengjia4574](<https://twitter.com/chengjia4574>)) and [pjf](<http://weibo.com/jfpan>) of IceSword Lab, Qihoo 360 Technology Co. Ltd: CVE-2016-10285, CVE-2016-10288, CVE-2016-10290, CVE-2017-0624, CVE-2017-0616, CVE-2017-0617, CVE-2016-10294, CVE-2016-10295, CVE-2016-10296\n * godzheng (\u90d1\u6587\u9009 [@VirtualSeekers](<https://twitter.com/virtualseekers>)) of Tencent PC Manager: CVE-2017-0602\n * [G\u00fcliz Seray Tuncay](<https://www.linkedin.com/in/g%C3%BCliz-seray-tuncay-952a1b9/>) of the [University of Illinois at Urbana-Champaign](<http://tuncay2.web.engr.illinois.edu>): CVE-2017-0593\n * Hao Chen and Guang Gong of Alpha Team, Qihoo 360 Technology Co. Ltd: CVE-2016-10283\n * Juhu Nie, Yang Cheng, Nan Li, and Qiwu Huang of Xiaomi Inc: CVE-2016-10276\n * [Micha\u0142 Bednarski](<https://github.com/michalbednarski>): CVE-2017-0598\n * Nathan Crandall ([@natecray](<https://twitter.com/natecray>)) of Tesla's Product Security Team: CVE-2017-0331, CVE-2017-0606\n * [Niky1235](<mailto:jiych.guru@gmail.com>) ([@jiych_guru](<https://twitter.com/jiych_guru>)): CVE-2017-0603\n * Peng Xiao, Chengming Yang, Ning You, Chao Yang, and Yang song of Alibaba Mobile Security Group: CVE-2016-10281, CVE-2016-10280\n * Roee Hay ([@roeehay](<https://twitter.com/roeehay>)) of [Aleph Research](<https://alephsecurity.com/>): CVE-2016-10277\n * [Scott Bauer](<mailto:sbauer@plzdonthack.me>) ([@ScottyBauer1](<https://twitter.com/ScottyBauer1>)): CVE-2016-10274\n * [Tong Lin](<mailto:segfault5514@gmail.com>), [Yuan-Tsung Lo](<mailto:computernik@gmail.com>), and Xuxian Jiang of [C0RE Team](<http://c0reteam.org>): CVE-2016-10291\n * Vasily Vasiliev: CVE-2017-0589\n * V.E.O ([@VYSEa](<https://twitter.com/vysea>)) of [Mobile Threat Response Team](<http://blog.trendmicro.com/trendlabs-security-intelligence/category/mobile>), [Trend Micro](<http://www.trendmicro.com>): CVE-2017-0590, CVE-2017-0587, CVE-2017-0600\n * Xiling Gong of Tencent Security Platform Department: CVE-2017-0597\n * Xingyuan Lin of 360 Marvel Team: CVE-2017-0627\n * Yong Wang (\u738b\u52c7) ([@ThomasKing2014](<https://twitter.com/ThomasKing2014>)) of Alibaba Inc: CVE-2017-0588\n * Yonggang Guo ([@guoygang](<https://twitter.com/guoygang>)) of IceSword Lab, Qihoo 360 Technology Co. Ltd: CVE-2016-10289, CVE-2017-0465\n * Yu Pan of Vulpecker Team, Qihoo 360 Technology Co. Ltd: CVE-2016-10282, CVE-2017-0615\n * Yu Pan and Peide Zhang of Vulpecker Team, Qihoo 360 Technology Co. Ltd: CVE-2017-0618, CVE-2017-0625\n\n## 2017-05-01 security patch level-Vulnerability details\n\nIn the sections below, we provide details for each of the security vulnerabilities that apply to the 2017-05-01 patch 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.\n\n### Remote code execution vulnerability in Mediaserver\n\nA remote code execution vulnerability in Mediaserver could enable an attacker using a specially crafted file to cause memory corruption during media file and data processing. This issue is rated as Critical due to the possibility of remote code execution within the context of the Mediaserver process.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0587 | [A-35219737](<https://android.googlesource.com/platform/external/libmpeg2/+/a86eb798d077b9b25c8f8c77e3c02c2f287c1ce7>) | Critical | All | 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2 | Jan 4, 2017 \nCVE-2017-0588 | [A-34618607](<https://android.googlesource.com/platform/frameworks/av/+/6f1d990ce0f116a205f467d9eb2082795e33872b>) | Critical | All | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2 | Jan 21, 2017 \nCVE-2017-0589 | [A-34897036](<https://android.googlesource.com/platform/external/libhevc/+/bcfc7124f6ef9f1ec128fb2e90de774a5b33d199>) | Critical | All | 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2 | Feb 1, 2017 \nCVE-2017-0590 | [A-35039946](<https://android.googlesource.com/platform/external/libhevc/+/45c97f878bee15cd97262fe7f57ecea71990fed7>) | Critical | All | 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2 | Feb 6, 2017 \nCVE-2017-0591 | [A-34097672](<https://android.googlesource.com/platform/external/libavc/+/5c3fd5d93a268abb20ff22f26009535b40db3c7d>) | Critical | All | 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2 | Google internal \nCVE-2017-0592 | [A-34970788](<https://android.googlesource.com/platform/frameworks/av/+/acc192347665943ca674acf117e4f74a88436922>) | Critical | All | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2 | Google internal \n \n### Elevation of privilege vulnerability in Framework APIs\n\nAn elevation of privilege vulnerability in the Framework APIs could enable a local malicious application to obtain access to custom permissions. This issue is rated as High because it is a general bypass for operating system protections that isolate application data from other applications.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0593 | [A-34114230](<https://android.googlesource.com/platform/frameworks/base/+/78efbc95412b8efa9a44d573f5767ae927927d48>) | High | All | 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2 | Jan 5, 2017 \n \n### Elevation of privilege vulnerability in Mediaserver\n\nAn elevation of privilege vulnerability in Mediaserver 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.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0594 | [A-34617444](<https://android.googlesource.com/platform/frameworks/av/+/594bf934384920618d2b6ce0bcda1f60144cb3eb>) | High | All | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2 | Jan 22, 2017 \nCVE-2017-0595 | [A-34705519](<https://android.googlesource.com/platform/frameworks/av/+/5443b57cc54f2e46b35246637be26a69e9f493e1>) | High | All | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1 | Jan 24, 2017 \nCVE-2017-0596 | [A-34749392](<https://android.googlesource.com/platform/frameworks/av/+/5443b57cc54f2e46b35246637be26a69e9f493e1>) | High | All | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1 | Jan 24, 2017 \n \n### Elevation of privilege vulnerability in Audioserver\n\nAn elevation of privilege vulnerability in Audioserver 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.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0597 | [A-34749571](<https://android.googlesource.com/platform/frameworks/av/+/a9188f89179a7edd301abaf37d644adf5d647a04>) | High | All | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2 | Jan 25, 2017 \n \n### Information disclosure vulnerability in Framework APIs\n\nAn information disclosure vulnerability in the Framework APIs 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 access to data that the application does not have access to.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0598 | [A-34128677](<https://android.googlesource.com/platform/frameworks/base/+/4e110ab20bb91e945a17c6e166e14e2da9608f08>) [[2](<https://android.googlesource.com/platform/frameworks/base/+/d42e1204d5dddb78ec9d20d125951b59a8344f40>)] | High | All | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2 | Jan 6, 2017 \n \n### Denial of service vulnerability in Mediaserver\n\nA remote 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 severity due to the possibility of remote denial of service.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0599 | [A-34672748](<https://android.googlesource.com/platform/external/libhevc/+/a1424724a00d62ac5efa0e27953eed66850d662f>) | High | All | 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2 | Jan 23, 2017 \nCVE-2017-0600 | [A-35269635](<https://android.googlesource.com/platform/frameworks/av/+/961e5ac5788b52304e64b9a509781beaf5201fb0>) | High | All | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2 | Feb 10, 2017 \n \n### Elevation of privilege vulnerability in Bluetooth\n\nAn Elevation of Privilege vulnerability in Bluetooth could potentially enable a local malicious application to accept harmful files shared via bluetooth without user permission. This issue is rated as Moderate due to local bypass of user interaction requirements. \n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0601 | [A-35258579](<https://android.googlesource.com/platform/frameworks/base/+/667d2cbe3eb1450f273a4f6595ccef35e1f0fe4b>) | Moderate | All | 7.0, 7.1.1, 7.1.2 | Feb 9, 2017 \n \n### Information disclosure vulnerability in File-Based Encryption\n\nAn information disclosure vulnerability in File-Based Encryption could enable a local malicious attacker to bypass operating system protections for the lock screen. This issue is rated as Moderate due to the possibility of bypassing the lock screen.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0493 | [A-32793550](<https://android.googlesource.com/platform/frameworks/base/+/e4cefbf4fce458489b5f1bebc79dfaf566bcc5d5>) [[2](<https://android.googlesource.com/platform/frameworks/base/+/f806d65e615b942c268a5f68d44bde9d55634972>)] [[3](<https://android.googlesource.com/platform/frameworks/base/+/58552f814a03d978b4a6507f3c16f71964f9b28f>)] | Moderate | All | 7.0, 7.1.1 | Nov 9, 2016 \n \n### Information disclosure vulnerability in Bluetooth\n\nAn information disclosure vulnerability in Bluetooth could allow a local malicious application to bypass operating system protections that isolate application data from other applications. This issue is rated as Moderate due to details specific to the vulnerability.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0602 | [A-34946955](<https://android.googlesource.com/platform/system/bt/+/a4875a49404c544134df37022ae587a4a3321647>) | Moderate | All | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2 | Dec 5, 2016 \n \n### Information disclosure vulnerability in OpenSSL & BoringSSL\n\nAn information disclosure vulnerability in OpenSSL & BoringSSL could enable a remote attacker to gain access to sensitive information. This issue is rated as Moderate due to details specific to the vulnerability.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2016-7056 | [A-33752052](<https://android.googlesource.com/platform/external/boringssl/+/13179a8e75fee98740b5ce728752aa7294b3e32d>) | Moderate | All | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2 | Dec 19, 2016 \n \n### Denial of service vulnerability in Mediaserver\n\nA 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 Moderate because it requires an uncommon device configuration.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0603 | [A-35763994](<https://android.googlesource.com/platform/frameworks/av/+/36b04932bb93cc3269279282686b439a17a89920>) | Moderate | All | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2 | Feb 23, 2017 \n \n### Denial of service vulnerability in Mediaserver\n\nA remote 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 Low due to details specific to the vulnerability.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0635 | [A-35467107](<https://android.googlesource.com/platform/frameworks/av/+/523f6b49c1a2289161f40cf9fe80b92e592e9441>) | Low | All | 7.0, 7.1.1, 7.1.2 | Feb 16, 2017 \n \n## 2017-05-05 security patch level-Vulnerability details\n\nIn the sections below, we provide details for each of the security vulnerabilities that apply to the 2017-05-05 patch 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.\n\n### Remote code execution vulnerability in GIFLIB\n\nA remote code execution vulnerability in GIFLIB could enable an attacker using a specially crafted file to cause memory corruption during media file and data processing. This issue is rated as Critical due to the possibility of remote code execution within the context of the Mediaserver process.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2015-7555 | [A-34697653](<https://android.googlesource.com/platform/external/giflib/+/dc07290edccc2c3fc4062da835306f809cea1fdc>) | Critical | All | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2 | April 13, 2016 \n \n### Elevation of privilege vulnerability in MediaTek touchscreen driver\n\nAn elevation of privilege vulnerability in the MediaTek touchscreen 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-10274 | A-30202412* M-ALPS02897901 | Critical | None** | Jul 16, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n** Supported Google devices on Android 7.1.1 or later that have installed all available updates are not affected by this vulnerability.\n\n### Elevation of privilege vulnerability in Qualcomm bootloader\n\nAn elevation of privilege vulnerability in the Qualcomm bootloader 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-10275 | A-34514954 [ QC-CR#1009111](<https://source.codeaurora.org/quic/la//kernel/lk/commit/?id=1a0a15c380e11fc46f8d8706ea5ae22b752bdd0b>) | Critical | Nexus 5X, Nexus 6, Pixel, Pixel XL, Android One | Sep 13, 2016 \nCVE-2016-10276 | A-32952839 [ QC-CR#1094105](<https://source.codeaurora.org/quic/la//kernel/lk/commit/?id=5dac431748027e8b50a5c4079967def4ea53ad64>) | Critical | Nexus 5X, Nexus 6P, Pixel, Pixel XL | Nov 16, 2016 \n \n### Elevation of privilege vulnerability in kernel sound subsystem\n\nAn elevation of privilege vulnerability in the kernel sound 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-9794 | A-34068036 [ Upstream kernel](<https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=a27178e05b7c332522df40904f27674e36ee3757>) | Critical | Nexus 5X, Nexus 6, Nexus 6P, Nexus 9, Pixel, Pixel XL, Pixel C, Android One, Nexus Player | Dec 3, 2016 \n \n### Elevation of privilege vulnerability in Motorola bootloader\n\nAn elevation of privilege vulnerability in the Motorola bootloader could enable a local malicious application to execute arbitrary code within the context of the bootloader. 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-10277 | A-33840490* | Critical | Nexus 6 | Dec 21, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Elevation of privilege vulnerability in NVIDIA video driver\n\nAn 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0331 | A-34113000* N-CVE-2017-0331 | Critical | Nexus 9 | Jan 4, 2017 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Elevation of privilege vulnerability in Qualcomm power driver\n\nAn elevation of privilege vulnerability in the kernel Qualcomm power 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0604 | A-35392981 [ QC-CR#826589](<https://source.codeaurora.org/quic/la//kernel/msm-3.18/commit/?id=6975e2dd5f37de965093ba3a8a08635a77a960f7>) | Critical | None* | Feb 15, 2017 \n \n* Supported Google devices on Android 7.1.1 or later that have installed all available updates are not affected by this vulnerability.\n\n### Vulnerabilities in Qualcomm components\n\nThese vulnerabilities affect Qualcomm components and are described in further detail in the Qualcomm AMSS August, September, October, and December 2016 security bulletins.\n\nCVE | References | Severity* | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-10240 | A-32578446** QC-CR#955710 | Critical | Nexus 6P | Qualcomm internal \nCVE-2016-10241 | A-35436149** QC-CR#1068577 | Critical | Nexus 5X, Nexus 6, Nexus 6P, Pixel, Pixel XL | Qualcomm internal \nCVE-2016-10278 | A-31624008** QC-CR#1043004 | High | Pixel, Pixel XL | Qualcomm internal \nCVE-2016-10279 | A-31624421** QC-CR#1031821 | High | Pixel, Pixel XL | Qualcomm internal \n \n* The severity rating for these vulnerabilities was determined by the vendor.\n\n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Remote code execution vulnerability in libxml2\n\nA remote code execution vulnerability in libxml2 could enable an attacker to use a specially crafted file to execute arbitrary code within 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 this library.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2016-5131 | A-32956747* | High | None** | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0 | July 23, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [Google Developer site](<https://developers.google.com/android/drivers>).\n\n** Supported Google devices on Android 7.1.1 or later that have installed all available updates are not affected by this vulnerability.\n\n### Elevation of privilege vulnerability in MediaTek thermal driver\n\nAn elevation of privilege vulnerability in the MediaTek thermal 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-10280 | A-28175767* M-ALPS02696445 | High | None** | Apr 11, 2016 \nCVE-2016-10281 | A-28175647* M-ALPS02696475 | High | None** | Apr 11, 2016 \nCVE-2016-10282 | A-33939045* M-ALPS03149189 | High | None** | Dec 27, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n** Supported Google devices on Android 7.1.1 or later that have installed all available updates are not affected by this vulnerability.\n\n### Elevation of privilege vulnerability in Qualcomm Wi-Fi driver\n\nAn elevation of privilege vulnerability in the Qualcomm 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-10283 | A-32094986 [ QC-CR#2002052](<https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=93863644b4547324309613361d70ad9dc91f8dfd>) | High | Nexus 5X, Pixel, Pixel XL, Android One | Oct 11, 2016 \n \n### Elevation of privilege vulnerability in Qualcomm video driver\n\nAn elevation of privilege vulnerability in the Qualcomm video 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-10284 | A-32402303* QC-CR#2000664 | High | Nexus 5X, Nexus 6, Nexus 6P, Pixel, Pixel XL, Android One | Oct 24, 2016 \nCVE-2016-10285 | A-33752702 [ QC-CR#1104899](<https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=67dfd3a65336e0b3f55ee83d6312321dc5f2a6f9>) | High | Pixel, Pixel XL | Dec 19, 2016 \nCVE-2016-10286 | A-35400904 [ QC-CR#1090237](<https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=5d30a3d0dc04916ddfb972bfc52f8e636642f999>) | High | Pixel, Pixel XL | Feb 15, 2017 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Elevation of privilege vulnerability in kernel performance subsystem\n\nAn 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2015-9004 | A-34515362 [ Upstream kernel](<https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=c3c87e770458aa004bd7ed3f29945ff436fd6511>) | High | Nexus 5X, Nexus 6, Nexus 6P, Nexus 9, Pixel, Pixel XL, Pixel C, Android One, Nexus Player | Nov 23, 2016 \n \n### Elevation of privilege vulnerability in Qualcomm sound driver\n\nAn 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-10287 | A-33784446 [ QC-CR#1112751](<https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm-4.4.git;a=commit;h=937bc9e644180e258c68662095861803f7ba4ded>) | High | Nexus 5X, Nexus 6P, Pixel, Pixel XL, Android One | Dec 20, 2016 \nCVE-2017-0606 | A-34088848 [ QC-CR#1116015](<https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm-4.4.git;a=commit;h=d3237316314c3d6f75a58192971f66e3822cd250>) | High | Nexus 5X, Nexus 6P, Pixel, Pixel XL, Android One | Jan 3, 2017 \nCVE-2016-5860 | A-34623424 [ QC-CR#1100682](<https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=9f91ae0d7203714fc39ae78e1f1c4fd71ed40498>) | High | Pixel, Pixel XL | Jan 22, 2017 \nCVE-2016-5867 | A-35400602 [ QC-CR#1095947](<https://source.codeaurora.org/quic/la//kernel/msm-3.18/commit/?id=065360da7147003aed8f59782b7652d565f56be5>) | High | None* | Feb 15, 2017 \nCVE-2017-0607 | A-35400551 [ QC-CR#1085928](<https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=b003c8d5407773d3aa28a48c9841e4c124da453d>) | High | Pixel, Pixel XL | Feb 15, 2017 \nCVE-2017-0608 | A-35400458 [ QC-CR#1098363](<https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=b66f442dd97c781e873e8f7b248e197f86fd2980>) | High | Nexus 5X, Nexus 6, Nexus 6P, Pixel, Pixel XL, Android One | Feb 15, 2017 \nCVE-2017-0609 | A-35399801 [ QC-CR#1090482](<https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=38a83df036084c00e8c5a4599c8ee7880b4ee567>) | High | Nexus 5X, Nexus 6P, Pixel, Pixel XL, Android One | Feb 15, 2017 \nCVE-2016-5859 | A-35399758 [ QC-CR#1096672](<https://source.codeaurora.org/quic/la//kernel/msm-3.18/commit/?id=97fdb441a9fb330a76245e473bc1a2155c809ebe>) | High | None* | Feb 15, 2017 \nCVE-2017-0610 | A-35399404 [ QC-CR#1094852](<https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=65009746a6e649779f73d665934561ea983892fe>) | High | Nexus 5X, Nexus 6, Nexus 6P, Pixel, Pixel XL, Android One | Feb 15, 2017 \nCVE-2017-0611 | A-35393841 [ QC-CR#1084210](<https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=1aa5df9246557a98181f03e98530ffd509b954c8>) | High | Nexus 5X, Nexus 6, Nexus 6P, Pixel, Pixel XL, Android One | Feb 15, 2017 \nCVE-2016-5853 | A-35392629 [ QC-CR#1102987](<https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=a8f3b894de319718aecfc2ce9c691514696805be>) | High | None* | Feb 15, 2017 \n \n* Supported Google devices on Android 7.1.1 or later that have installed all available updates are not affected by this vulnerability.\n\n### Elevation of privilege vulnerability in Qualcomm LED driver\n\nAn elevation of privilege vulnerability in the Qualcomm LED 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-10288 | A-33863909 [ QC-CR#1109763](<https://source.codeaurora.org/quic/la//kernel/msm-3.18/commit/?id=db2cdc95204bc404f03613d5dd7002251fb33660>) | High | Pixel, Pixel XL | Dec 23, 2016 \n \n### Elevation of privilege vulnerability in Qualcomm crypto driver\n\nAn elevation of privilege vulnerability in the Qualcomm crypto 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-10289 | A-33899710 [ QC-CR#1116295](<https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=a604e6f3889ccc343857532b63dea27603381816>) | High | Nexus 5X, Nexus 6, Nexus 6P, Pixel, Pixel XL, Android One | Dec 24, 2016 \n \n### Elevation of privilege vulnerability in Qualcomm shared memory driver\n\nAn elevation of privilege vulnerability in the Qualcomm shared memory 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-10290 | A-33898330 [ QC-CR#1109782](<https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=a5e46d8635a2e28463b365aacdeab6750abd0d49>) | High | Nexus 5X, Nexus 6P, Pixel, Pixel XL | Dec 24, 2016 \n \n### Elevation of privilege vulnerability in Qualcomm Slimbus driver\n\nAn elevation of privilege vulnerability in the Qualcomm Slimbus 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-10291 | A-34030871 [ QC-CR#986837](<https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=a225074c0494ca8125ca0ac2f9ebc8a2bd3612de>) | High | Nexus 5X, Nexus 6, Nexus 6P, Android One | Dec 31, 2016 \n \n### Elevation of privilege vulnerability in Qualcomm ADSPRPC driver\n\nAn elevation of privilege vulnerability in the Qualcomm ADSPRPC 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0465 | A-34112914 [ QC-CR#1110747](<https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=3823f0f8d0bbbbd675a42a54691f4051b3c7e544>) | High | Nexus 5X, Nexus 6P, Pixel, Pixel XL, Android One | Jan 5, 2017 \n \n### Elevation of privilege vulnerability in Qualcomm Secure Execution Environment Communicator driver\n\nAn elevation of privilege vulnerability in the Qualcomm Secure Execution Environment Communicator 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0612 | A-34389303 [ QC-CR#1061845](<https://source.codeaurora.org/quic/la//kernel/msm-3.18/commit/?id=05efafc998dc86c3b75af9803ca71255ddd7a8eb>) | High | Pixel, Pixel XL | Jan 10, 2017 \nCVE-2017-0613 | A-35400457 [ QC-CR#1086140](<https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=b108c651cae9913da1ab163cb4e5f7f2db87b747>) | High | Nexus 5X, Nexus 6, Nexus 6P, Pixel, Pixel XL, Android One | Feb 15, 2017 \nCVE-2017-0614 | A-35399405 [ QC-CR#1080290](<https://source.codeaurora.org/quic/la//kernel/msm-3.18/commit/?id=fc2ae27eb9721a0ce050c2062734fec545cda604>) | High | Nexus 5X, Nexus 6, Nexus 6P, Pixel, Pixel XL, Android One | Feb 15, 2017 \n \n### Elevation of privilege vulnerability in MediaTek power driver\n\nAn elevation of privilege vulnerability in the MediaTek power 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0615 | A-34259126* M-ALPS03150278 | High | None** | Jan 12, 2017 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n** Supported Google devices on Android 7.1.1 or later that have installed all available updates are not affected by this vulnerability.\n\n### Elevation of privilege vulnerability in MediaTek system management interrupt driver\n\nAn elevation of privilege vulnerability in the MediaTek system management interrupt 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0616 | A-34470286* M-ALPS03149160 | High | None** | Jan 19, 2017 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n** Supported Google devices on Android 7.1.1 or later that have installed all available updates are not affected by this vulnerability.\n\n### Elevation of privilege vulnerability in MediaTek video driver\n\nAn elevation of privilege vulnerability in the MediaTek video 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0617 | A-34471002* M-ALPS03149173 | High | None** | Jan 19, 2017 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n** Supported Google devices on Android 7.1.1 or later that have installed all available updates are not affected by this vulnerability.\n\n### Elevation of privilege vulnerability in MediaTek command queue driver\n\nAn elevation of privilege vulnerability in the MediaTek command queue 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0618 | A-35100728* M-ALPS03161536 | High | None** | Feb 7, 2017 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n** Supported Google devices on Android 7.1.1 or later that have installed all available updates are not affected by this vulnerability.\n\n### Elevation of privilege vulnerability in Qualcomm pin controller driver\n\nAn elevation of privilege vulnerability in the Qualcomm pin controller 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0619 | A-35401152 [ QC-CR#826566](<https://source.codeaurora.org/quic/la//kernel/msm-3.14/commit/?id=72f67b29a9c5e6e8d3c34751600c749c5f5e13e1>) | High | Nexus 6, Android One | Feb 15, 2017 \n \n### Elevation of privilege vulnerability in Qualcomm Secure Channel Manager Driver\n\nAn elevation of privilege vulnerability in the Qualcomm Secure Channel Manager 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0620 | A-35401052 [ QC-CR#1081711](<https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=01b2c9a5d728ff6f2f1f28a5d4e927aaeabf56ed>) | High | Nexus 5X, Nexus 6, Nexus 6P, Pixel, Pixel XL, Android One | Feb 15, 2017 \n \n### Elevation of privilege vulnerability in Qualcomm sound codec driver\n\nAn elevation of privilege vulnerability in the Qualcomm 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-5862 | A-35399803 [ QC-CR#1099607](<https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=4199451e83729a3add781eeafaee32994ff65b04>) | High | Pixel, Pixel XL | Feb 15, 2017 \n \n### Elevation of privilege vulnerability in kernel voltage regulator driver\n\nAn elevation of privilege vulnerability in the kernel voltage regulator 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2014-9940 | A-35399757 [ Upstream kernel](<https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=60a2362f769cf549dc466134efe71c8bf9fbaaba>) | High | Nexus 6, Nexus 9, Pixel C, Android One, Nexus Player | Feb 15, 2017 \n \n### Elevation of privilege vulnerability in Qualcomm camera driver\n\nAn 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0621 | A-35399703 [ QC-CR#831322](<https://source.codeaurora.org/quic/la//kernel/msm-3.10/commit/?id=9656e2c2b3523af20502bf1e933e35a397f5e82f>) | High | Android One | Feb 15, 2017 \n \n### Elevation of privilege vulnerability in Qualcomm networking driver\n\nAn elevation of privilege vulnerability in the Qualcomm networking 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-5868 | A-35392791 [ QC-CR#1104431](<https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=fbb765a3f813f5cc85ddab21487fd65f24bf6a8c>) | High | Nexus 5X, Pixel, Pixel XL | Feb 15, 2017 \n \n### Elevation of privilege vulnerability in kernel networking subsystem\n\nAn 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 High because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-7184 | A-36565222 [ Upstream kernel](<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=677e806da4d916052585301785d847c3b3e6186a>) [ [2]](<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f843ee6dd019bcece3e74e76ad9df0155655d0df>) | High | Nexus 5X, Nexus 6, Nexus 6P, Nexus 9, Pixel, Pixel XL, Android One | Mar 23, 2017 \n \n### Elevation of privilege vulnerability in Goodix touchscreen driver\n\nAn elevation of privilege vulnerability in the Goodix 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0622 | A-32749036 [ QC-CR#1098602](<https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=40efa25345003a96db34effbd23ed39530b3ac10>) | High | Android One | Google internal \n \n### Elevation of privilege vulnerability in HTC bootloader\n\nAn elevation of privilege vulnerability in the HTC bootloader could enable a local malicious application to execute arbitrary code within the context of the bootloader. This issue is rated as High because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0623 | A-32512358* | High | Pixel, Pixel XL | Google Internal \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Information disclosure vulnerability in Qualcomm Wi-Fi driver\n\nAn information disclosure vulnerability in the Qualcomm Wi-Fi 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0624 | A-34327795* QC-CR#2005832 | High | Nexus 5X, Pixel, Pixel XL | Jan 16, 2017 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Information disclosure vulnerability in MediaTek command queue driver\n\nAn information disclosure vulnerability in the MediaTek command queue 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0625 | A-35142799* M-ALPS03161531 | High | None** | Feb 8, 2017 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n** Supported Google devices on Android 7.1.1 or later that have installed all available updates are not affected by this vulnerability.\n\n### Information disclosure vulnerability in Qualcomm crypto engine driver\n\nAn information disclosure vulnerability in the Qualcomm crypto engine 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0626 | A-35393124 [ QC-CR#1088050](<https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=64551bccab9b5b933757f6256b58f9ca0544f004>) | High | Nexus 5X, Nexus 6, Nexus 6P, Pixel, Pixel XL, Android One | Feb 15, 2017 \n \n### Denial of service vulnerability in Qualcomm Wi-Fi driver\n\nA denial of service vulnerability in the Qualcomm Wi-Fi driver could enable a proximate attacker to cause a denial of service in the Wi-Fi subsystem. This issue is rated as High due to the possibility of remote denial of service.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-10292 | A-34514463* QC-CR#1065466 | High | Nexus 5X, Pixel, Pixel XL | Dec 16, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Information disclosure vulnerability in kernel UVC driver\n\nAn information disclosure vulnerability in the kernel UVC 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0627 | A-33300353* | Moderate | Nexus 5X, Nexus 6P, Nexus 9, Pixel C, Nexus Player | Dec 2, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Information disclosure vulnerability in Qualcomm video driver\n\nAn information disclosure vulnerability in the Qualcomm 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-10293 | A-33352393 [ QC-CR#1101943](<https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=2469d5374745a2228f774adbca6fb95a79b9047f>) | Moderate | Nexus 5X, Nexus 6P, Android One | Dec 4, 2016 \n \n### Information disclosure vulnerability in Qualcomm power driver (device specific)\n\nAn information disclosure vulnerability in the Qualcomm power 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-10294 | A-33621829 [ QC-CR#1105481](<https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=9e9bc51ffb8a298f0be5befe346762cdb6e1d49c>) | Moderate | Nexus 5X, Nexus 6P, Pixel, Pixel XL | Dec 14, 2016 \n \n### Information disclosure vulnerability in Qualcomm LED driver\n\nAn information disclosure vulnerability in the Qualcomm LED 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-10295 | A-33781694 [ QC-CR#1109326](<https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=f11ae3df500bc2a093ddffee6ea40da859de0fa9>) | Moderate | Pixel, Pixel XL | Dec 20, 2016 \n \n### Information disclosure vulnerability in Qualcomm shared memory driver\n\nAn information disclosure vulnerability in the Qualcomm shared memory 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-10296 | A-33845464 [ QC-CR#1109782](<https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=a5e46d8635a2e28463b365aacdeab6750abd0d49>) | Moderate | Nexus 5X, Nexus 6P, Pixel, Pixel XL, Android One | Dec 22, 2016 \n \n### Information disclosure vulnerability in Qualcomm camera driver\n\nAn information disclosure vulnerability in the Qualcomm camera 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0628 | A-34230377 [ QC-CR#1086833](<https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=012e37bf91490c5b59ba2ab68a4d214b632b613f>) | Moderate | Nexus 5X, Nexus 6, Pixel, Pixel XL | Jan 10, 2017 \nCVE-2017-0629 | A-35214296 [ QC-CR#1086833](<https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=012e37bf91490c5b59ba2ab68a4d214b632b613f>) | Moderate | Nexus 5X, Nexus 6, Pixel, Pixel XL | Feb 8, 2017 \n \n### Information disclosure vulnerability in kernel trace subsystem\n\nAn information disclosure vulnerability in the kernel trace 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0630 | A-34277115* | Moderate | Nexus 5X, Nexus 6, Nexus 6P, Nexus 9, Pixel, Pixel XL, Pixel C, Android One, Nexus Player | Jan 11, 2017 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Information disclosure vulnerability in Qualcomm sound codec driver\n\nAn information disclosure vulnerability in the Qualcomm sound codec 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-5858 | A-35400153 [ QC-CR#1096799](<https://source.codeaurora.org/quic/la//kernel/msm-3.18/commit/?id=3154eb1d263b9c3eab2c9fa8ebe498390bf5d711>) [ [2]](<https://source.codeaurora.org/quic/la//kernel/msm-3.18/commit/?id=afc5bea71bc8f251dad1104568383019f4923af6>) | Moderate | Nexus 5X, Nexus 6, Nexus 6P, Pixel, Pixel XL, Android One | Feb 15, 2017 \n \n### Information disclosure vulnerability in Qualcomm camera driver\n\nAn information disclosure vulnerability in the Qualcomm camera 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0631 | A-35399756 [ QC-CR#1093232](<https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=8236d6ebc7e26361ca7078cbeba01509f10941d8>) | Moderate | Nexus 5X, Nexus 6P, Pixel, Pixel XL, Android One | Feb 15, 2017 \n \n### Information disclosure vulnerability in Qualcomm sound driver\n\nAn 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-5347 | A-35394329 [ QC-CR#1100878](<https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=f14390f13e62460fc6b05fc0acde0e825374fdb6>) | Moderate | Nexus 5X, Nexus 6, Nexus 6P, Pixel, Pixel XL, Android One | Feb 15, 2017 \n \n### Information disclosure vulnerability in Qualcomm SPCom driver\n\nAn information disclosure vulnerability in the Qualcomm SPCom 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-5854 | A-35392792 [ QC-CR#1092683](<https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=28d23d4d7999f683b27b6e0c489635265b67a4c9>) | Moderate | None* | Feb 15, 2017 \nCVE-2016-5855 | A-35393081 [ QC-CR#1094143](<https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=a5edb54e93ba85719091fe2bc426d75fa7059834>) | Moderate | None* | Feb 15, 2017 \n \n* Supported Google devices on Android 7.1.1 or later that have installed all available updates are not affected by this vulnerability.\n\n### Information disclosure vulnerability in Qualcomm sound codec driver\n\nAn information disclosure vulnerability in the Qualcomm sound codec 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0632 | A-35392586 [ QC-CR#832915](<https://source.codeaurora.org/quic/la//kernel/msm-3.10/commit/?id=970d6933e53c1f7ca8c8b67f49147b18505c3b8f>) | Moderate | Android One | Feb 15, 2017 \n \n### Information disclosure vulnerability in Broadcom Wi-Fi driver\n\nAn information disclosure vulnerability in the Broadcom Wi-Fi driver could enable a local malicious component to access data outside of its permission levels. This issue is rated as Moderate because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0633 | A-36000515* B-RB#117131 | Moderate | Nexus 6, Nexus 6P, Nexus 9, Pixel C, Nexus Player | Feb 23, 2017 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Information disclosure vulnerability in Synaptics touchscreen driver\n\nAn information disclosure vulnerability in the Synaptics touchscreen 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.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0634 | A-32511682* | Moderate | Pixel, Pixel XL | Google internal \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Vulnerabilities in Qualcomm components\n\nThese vulnerabilities affecting Qualcomm components were released as part of Qualcomm AMSS security bulletins between 2014\u20132016. They are included in this Android security bulletin to associate their fixes with an Android security patch level.\n\nCVE | References | Severity* | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2014-9923 | A-35434045** | Critical | None*** | Qualcomm internal \nCVE-2014-9924 | A-35434631** | Critical | None*** | Qualcomm internal \nCVE-2014-9925 | A-35444657** | Critical | None*** | Qualcomm internal \nCVE-2014-9926 | A-35433784** | Critical | None*** | Qualcomm internal \nCVE-2014-9927 | A-35433785** | Critical | None*** | Qualcomm internal \nCVE-2014-9928 | A-35438623** | Critical | None*** | Qualcomm internal \nCVE-2014-9929 | A-35443954** QC-CR#644783 | Critical | None*** | Qualcomm internal \nCVE-2014-9930 | A-35432946** | Critical | None*** | Qualcomm internal \nCVE-2015-9005 | A-36393500** | Critical | None*** | Qualcomm internal \nCVE-2015-9006 | A-36393450** | Critical | None*** | Qualcomm internal \nCVE-2015-9007 | A-36393700** | Critical | None*** | Qualcomm internal \nCVE-2016-10297 | A-36393451** | Critical | None*** | Qualcomm internal \nCVE-2014-9941 | A-36385125** | High | None*** | Qualcomm internal \nCVE-2014-9942 | A-36385319** | High | None*** | Qualcomm internal \nCVE-2014-9943 | A-36385219** | High | None*** | Qualcomm internal \nCVE-2014-9944 | A-36384534** | High | None*** | Qualcomm internal \nCVE-2014-9945 | A-36386912** | High | None*** | Qualcomm internal \nCVE-2014-9946 | A-36385281** | High | None*** | Qualcomm internal \nCVE-2014-9947 | A-36392400** | High | None*** | Qualcomm internal \nCVE-2014-9948 | A-36385126** | High | None*** | Qualcomm internal \nCVE-2014-9949 | A-36390608** | High | None*** | Qualcomm internal \nCVE-2014-9950 | A-36385321** | High | None*** | Qualcomm internal \nCVE-2014-9951 | A-36389161** | High | None*** | Qualcomm internal \nCVE-2014-9952 | A-36387019** | High | None*** | Qualcomm internal \n \n* The severity rating for these vulnerabilities was determined by the vendor.\n\n** The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n*** Supported Google devices on Android 7.1.1 or later that have installed all available updates are not affected by this vulnerability.\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, read the instructions on the [Pixel and Nexus update schedule](<https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices>).\n\n * Security patch levels of 2017-05-01 or later address all issues associated with the 2017-05-01 security patch level.\n * Security patch levels of 2017-05-05 or later address all issues associated with the 2017-05-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]:[2017-05-01]\n * [ro.build.version.security_patch]:[2017-05-05]\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 May 01, 2017 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 May 05, 2017 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\\. How do I determine which Google devices are affected by each issue?**\n\nIn the 2017-05-01 and 2017-05-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:\n\n * **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](<https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices>): Nexus 5X, Nexus 6, Nexus 6P, Nexus 9, Android One, Nexus Player, Pixel C, Pixel, and Pixel XL.\n * **Some Google devices**: If an issue doesn't affect all Google devices, the affected Google devices are listed in the _Updated Google devices_ column.\n * **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. \n\n**4\\. What do the entries in the references column map to?**\n\nEntries 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:\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## Revisions\n\n * May 01, 2017: Bulletin published.\n * May 02, 2017: Bulletin revised to include AOSP links.\n * August 10, 2017: Bulletin revised to include additional AOSP link for CVE-2017-0493.\n * August 17, 2017: Bulletin revised to update reference numbers.\n * October 03, 2017: Bulletin revised to remove CVE-2017-0605.\n", "cvss3": {"exploitabilityScore": 2.8, "cvssV3": {"baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "attackComplexity": "LOW", "scope": "UNCHANGED", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "baseScore": 8.8, "vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "version": "3.0", "userInteraction": "REQUIRED"}, "impactScore": 5.9}, "published": "2017-05-01T00:00:00", "type": "androidsecurity", "title": "Android Security Bulletin\u2014May 2017", "bulletinFamily": "software", "cvss2": {"severity": "HIGH", "exploitabilityScore": 8.6, "obtainAllPrivilege": false, "userInteractionRequired": true, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "MEDIUM", "confidentialityImpact": "COMPLETE", "availabilityImpact": "COMPLETE", "integrityImpact": "COMPLETE", "baseScore": 9.3, "vectorString": "AV:N/AC:M/Au:N/C:C/I:C/A:C", "version": "2.0", "accessVector": "NETWORK", "authentication": "NONE"}, "impactScore": 10.0, "obtainUserPrivilege": false}, "cvelist": ["CVE-2014-9923", "CVE-2014-9924", "CVE-2014-9925", "CVE-2014-9926", "CVE-2014-9927", "CVE-2014-9928", "CVE-2014-9929", "CVE-2014-9930", "CVE-2014-9940", "CVE-2014-9941", "CVE-2014-9942", "CVE-2014-9943", "CVE-2014-9944", "CVE-2014-9945", "CVE-2014-9946", "CVE-2014-9947", "CVE-2014-9948", "CVE-2014-9949", "CVE-2014-9950", "CVE-2014-9951", "CVE-2014-9952", "CVE-2015-7555", "CVE-2015-9004", "CVE-2015-9005", "CVE-2015-9006", "CVE-2015-9007", "CVE-2016-10240", "CVE-2016-10241", "CVE-2016-10274", "CVE-2016-10275", "CVE-2016-10276", "CVE-2016-10277", "CVE-2016-10278", "CVE-2016-10279", "CVE-2016-10280", "CVE-2016-10281", "CVE-2016-10282", "CVE-2016-10283", "CVE-2016-10284", "CVE-2016-10285", "CVE-2016-10286", "CVE-2016-10287", "CVE-2016-10288", "CVE-2016-10289", "CVE-2016-10290", "CVE-2016-10291", "CVE-2016-10292", "CVE-2016-10293", "CVE-2016-10294", "CVE-2016-10295", "CVE-2016-10296", "CVE-2016-10297", "CVE-2016-5131", "CVE-2016-5347", "CVE-2016-5853", "CVE-2016-5854", "CVE-2016-5855", "CVE-2016-5858", "CVE-2016-5859", "CVE-2016-5860", "CVE-2016-5862", "CVE-2016-5867", "CVE-2016-5868", "CVE-2016-7056", "CVE-2016-9794", "CVE-2017-0331", "CVE-2017-0465", "CVE-2017-0493", "CVE-2017-0587", "CVE-2017-0588", "CVE-2017-0589", "CVE-2017-0590", "CVE-2017-0591", "CVE-2017-0592", "CVE-2017-0593", "CVE-2017-0594", "CVE-2017-0595", "CVE-2017-0596", "CVE-2017-0597", "CVE-2017-0598", "CVE-2017-0599", "CVE-2017-0600", "CVE-2017-0601", "CVE-2017-0602", "CVE-2017-0603", "CVE-2017-0604", "CVE-2017-0605", "CVE-2017-0606", "CVE-2017-0607", "CVE-2017-0608", "CVE-2017-0609", "CVE-2017-0610", "CVE-2017-0611", "CVE-2017-0612", "CVE-2017-0613", "CVE-2017-0614", "CVE-2017-0615", "CVE-2017-0616", "CVE-2017-0617", "CVE-2017-0618", "CVE-2017-0619", "CVE-2017-0620", "CVE-2017-0621", "CVE-2017-0622", "CVE-2017-0623", "CVE-2017-0624", "CVE-2017-0625", "CVE-2017-0626", "CVE-2017-0627", "CVE-2017-0628", "CVE-2017-0629", "CVE-2017-0630", "CVE-2017-0631", "CVE-2017-0632", "CVE-2017-0633", "CVE-2017-0634", "CVE-2017-0635", "CVE-2017-7184"], "modified": "2017-10-03T00:00:00", "id": "ANDROID:2017-05-01", "href": "https://source.android.com/docs/security/bulletin/2017-05-01", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}}]}
CVE-2017-0596
