Vulnerabilities > Google
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2024-11-19 | CVE-2018-9424 | Out-of-bounds Write vulnerability in Google Android 8.0/8.1 In CryptoPlugin::decrypt of CryptoPlugin.cpp, there is a possible out of bounds write due to a missing bounds check. | 7.8 |
| 2024-11-19 | CVE-2018-9428 | Use After Free vulnerability in Google Android 8.1 In startDevice of AAudioServiceStreamBase.cpp there is a possible out of bounds write due to a use after free. | 7.8 |
| 2024-11-19 | CVE-2018-9432 | Unspecified vulnerability in Google Android In createPhonebookDialogView and createMapDialogView of BluetoothPermissionActivity.java, there is a possible permissions bypass. | 7.8 |
| 2024-11-19 | CVE-2018-9433 | Unspecified vulnerability in Google Android In ArrayConcatVisitor of builtins-array.cc, there is a possible type confusion due to improper input validation. | 8.8 |
| 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-9364 | Unspecified vulnerability in Google Android In the LG LAF component, there is a special command that allowed modification of certain partitions. | 7.5 |
| 2024-11-19 | CVE-2018-9366 | Integer Overflow or Wraparound vulnerability in Google Android In IMSA_Recv_Thread and VT_IMCB_Thread of ImsaClient.cpp and VideoTelephony.c, there is a possible out of bounds write due to an integer overflow. | 7.8 |
| 2024-11-19 | CVE-2018-9367 | Out-of-bounds Write vulnerability in Google Android In FT_ACDK_CCT_V2_OP_ISP_SET_TUNING_PARAS of Meta_CCAP_Para.cpp, there is a possible out of bounds write due to improper input validation. | 7.8 |
| 2024-11-19 | CVE-2018-9368 | Out-of-bounds Write vulnerability in Google Android In mtkscoaudio debugfs there is a possible arbitrary kernel memory write due to missing bounds check and weakened SELinux policies. | 7.8 |