Vulnerabilities > Google > Android > Critical
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2018-04-04 | CVE-2016-10230 | Permissions, Privileges, and Access Controls vulnerability in Google Android A remote code execution vulnerability in the Qualcomm crypto driver. | 9.8 |
2018-04-04 | CVE-2016-10233 | Permissions, Privileges, and Access Controls vulnerability in Google Android An elevation of privilege vulnerability in the Qualcomm video driver. | 9.8 |
2018-04-04 | CVE-2016-10298 | Permissions, Privileges, and Access Controls vulnerability in Google Android An elevation of privilege vulnerability in Qualcomm closed source components. | 9.8 |
2018-04-04 | CVE-2016-10299 | Permissions, Privileges, and Access Controls vulnerability in Google Android An elevation of privilege vulnerability in Qualcomm closed source components. | 9.8 |
2018-04-04 | CVE-2016-8484 | Permissions, Privileges, and Access Controls vulnerability in Google Android An elevation of privilege vulnerability in Qualcomm closed source components. | 9.8 |
2018-04-04 | CVE-2016-8487 | Permissions, Privileges, and Access Controls vulnerability in Google Android An elevation of privilege vulnerability in Qualcomm closed source components. | 9.8 |
2018-04-04 | CVE-2016-8488 | Permissions, Privileges, and Access Controls vulnerability in Google Android An elevation of privilege vulnerability in Qualcomm closed source components. | 9.8 |
2018-04-04 | CVE-2017-13266 | Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in Google Android In avrc_pars_vendor_cmd of avrc_pars_tg.cc, there is a possible stack corruption due to a missing bounds check. | 9.8 |
2018-04-04 | CVE-2017-13272 | Use After Free vulnerability in Google Android In alarm_ready_generic of alarm.cc, there is a possible out of bounds write due to a use after free. | 9.8 |
2018-04-04 | CVE-2017-13267 | Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in Google Android In avrc_pars_vendor_cmd of avrc_pars_tg.cc, there is a possible stack corruption due to a missing bounds check. | 9.8 |