Vulnerabilities > Google > Android > High
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2024-12-02 | CVE-2018-9380 | Out-of-bounds Write vulnerability in Google Android In l2c_lcc_proc_pdu of l2c_fcr.cc, there is a possible out of bounds write due to improper input validation. | 8.8 |
| 2024-12-02 | CVE-2018-9381 | Use of Uninitialized Resource vulnerability in Google Android 8.1 In gatts_process_read_by_type_req of gatt_sr.c, there is a possible information disclosure due to uninitialized data. | 7.5 |
| 2024-12-02 | CVE-2024-20129 | Out-of-bounds Read vulnerability in Google Android 13.0/14.0/15.0 In Telephony, there is a possible out of bounds read due to a missing bounds check. | 7.5 |
| 2024-11-28 | CVE-2018-9374 | Unspecified vulnerability in Google Android In installPackageLI of PackageManagerService.java, there is a possible permissions bypass. | 7.8 |
| 2024-11-27 | CVE-2017-13323 | Integer Overflow or Wraparound vulnerability in Google Android In String16 of String16.cpp, there is a possible out of bounds write due to an integer overflow. | 7.8 |
| 2024-11-27 | CVE-2017-13316 | Missing Authorization vulnerability in Google Android In checkPermissions of RecognitionService.java, there is a possible permissions bypass due to a missing permission check. | 7.8 |
| 2024-11-27 | CVE-2017-13319 | Classic Buffer Overflow vulnerability in Google Android In pvmp3_get_main_data_size of pvmp3_get_main_data_size.cpp, there is a possible buffer overread due to a missing bounds check. | 7.5 |
| 2024-11-20 | CVE-2018-9470 | Out-of-bounds Write vulnerability in Google Android In bff_Scanner_addOutPos of Scanner.c, there is a possible out-of-bounds write due to an incorrect bounds check. | 8.8 |
| 2024-11-20 | CVE-2018-9471 | Type Confusion vulnerability in Google Android In the deserialization constructor of NanoAppFilter.java, there is a possible loss of data due to type confusion. | 7.8 |
| 2024-11-20 | CVE-2018-9472 | Integer Overflow or Wraparound vulnerability in Google Android In xmlMemStrdupLoc of xmlmemory.c, there is a possible out-of-bounds write due to an integer overflow. | 8.8 |