Vulnerabilities > Google > Medium
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2024-11-20 | CVE-2018-9485 | Out-of-bounds Read vulnerability in Google Android In l2cble_process_sig_cmd of l2c_ble.cc, there is a possible out of bounds read due to a missing bounds check. | 6.5 |
| 2024-11-20 | CVE-2018-9486 | Out-of-bounds Read vulnerability in Google Android In hidh_l2cif_data_ind of hidh_conn.cc, there is a possible out of bounds read due to a missing bounds check. | 6.5 |
| 2024-11-20 | CVE-2018-9487 | Unspecified vulnerability in Google Android 8.0/8.1/9.0 In setVpnForcedLocked of Vpn.java, there is a possible blocking of internet traffic through vpn due to a bad uid check. | 5.5 |
| 2024-11-19 | CVE-2018-9440 | Unspecified vulnerability in Google Android In parse of M3UParser.cpp there is a possible resource exhaustion due to improper input validation. | 6.5 |
| 2024-11-19 | CVE-2018-9412 | Unspecified vulnerability in Google Android In removeUnsynchronization of ID3.cpp there is a possible resource exhaustion due to improper input validation. | 5.5 |
| 2024-11-19 | CVE-2018-9420 | Use of Uninitialized Resource vulnerability in Google Android In BnCameraService::onTransact of CameraService.cpp, there is a possible information disclosure due to uninitialized data. | 5.5 |
| 2024-11-19 | CVE-2018-9421 | Use of Uninitialized Resource vulnerability in Google Android In writeInplace of Parcel.cpp, there is a possible information leak across processes, using Binder, due to uninitialized data. | 5.5 |
| 2024-11-19 | CVE-2018-9410 | Out-of-bounds Read vulnerability in Google Android 8.0/8.1 In analyzeAxes of FontUtils.cpp, there is a possible out of bounds read due to a missing bounds check. | 5.5 |
| 2024-11-19 | CVE-2018-9348 | Integer Overflow or Wraparound vulnerability in Google Android In SMF_ParseMetaEvent of eas_smf.c, there is a possible integer overflow. | 6.5 |
| 2024-11-19 | CVE-2018-9371 | Out-of-bounds Write vulnerability in Google Android In the Mediatek Preloader, there are out of bounds reads and writes due to an exposed interface that allows arbitrary peripheral memory mapping with insufficient blacklisting/whitelisting. | 6.4 |