Vulnerabilities > Google > Low
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2022-02-11 | CVE-2021-39687 | Out-of-bounds Read vulnerability in Google Android In HandleTransactionIoEvent of actuator_driver.cc, there is a possible out of bounds read due to a heap buffer overflow. | 2.1 |
2022-02-11 | CVE-2021-39666 | Out-of-bounds Read vulnerability in Google Android 11.0/12.0 In extract of MediaMetricsItem.h, there is a possible out of bounds read due to improper input validation. | 2.1 |
2022-02-11 | CVE-2021-39664 | Out-of-bounds Read vulnerability in Google Android 12.0 In LoadedPackage::Load of LoadedArsc.cpp, there is a possible out of bounds read due to a missing bounds check. | 1.9 |
2022-02-11 | CVE-2021-0524 | Information Exposure Through Discrepancy vulnerability in Google Android 12.0 In isServiceDistractionOptimized of CarPackageManagerService.java, there is a possible disclosure of installed packages due to side channel information disclosure. | 2.1 |
2022-02-09 | CVE-2022-20046 | Memory Leak vulnerability in Google Android In Bluetooth, there is a possible memory corruption due to a logic error. | 2.1 |
2022-02-09 | CVE-2022-20042 | Improper Handling of Exceptional Conditions vulnerability in Google Android In Bluetooth, there is a possible information disclosure due to incorrect error handling. | 2.1 |
2022-02-09 | CVE-2022-20035 | Use After Free vulnerability in Google Android 10.0/11.0 In vcu driver, there is a possible information disclosure due to a use after free. | 2.1 |
2022-02-09 | CVE-2022-20033 | Out-of-bounds Read vulnerability in Google Android 11.0/12.0 In camera driver, there is a possible out of bounds read due to an incorrect bounds check. | 2.1 |
2022-02-09 | CVE-2022-20032 | Race Condition vulnerability in Google Android 10.0/11.0/12.0 In vow driver, there is a possible memory corruption due to a race condition. | 1.9 |
2022-02-09 | CVE-2022-20029 | Out-of-bounds Read vulnerability in Google Android 10.0/11.0/12.0 In cmdq driver, there is a possible out of bounds read due to an incorrect bounds check. | 2.1 |