Vulnerabilities > Google > Android > 4.2.2
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2023-12-08 | CVE-2023-45866 | Improper Authentication vulnerability in multiple products Bluetooth HID Hosts in BlueZ may permit an unauthenticated Peripheral role HID Device to initiate and establish an encrypted connection, and accept HID keyboard reports, potentially permitting injection of HID messages when no user interaction has occurred in the Central role to authorize such access. | 6.3 |
2023-10-30 | CVE-2023-21372 | Out-of-bounds Read vulnerability in Google Android In libdexfile, there is a possible out of bounds read due to a missing bounds check. | 7.8 |
2023-10-30 | CVE-2023-21375 | Integer Overflow or Wraparound vulnerability in Google Android In Sysproxy, there is a possible out of bounds write due to an integer underflow. | 7.8 |
2023-10-30 | CVE-2023-21376 | Unspecified vulnerability in Google Android In Telephony, there is a possible way to retrieve the ICCID due to a logic error in the code. | 5.5 |
2023-10-30 | CVE-2023-21377 | Unspecified vulnerability in Google Android In SELinux Policy, there is a possible restriction bypass due to a permissions bypass. | 5.5 |
2023-10-30 | CVE-2023-21378 | Missing Authorization vulnerability in Google Android In Telecomm, there is a possible way to silence the ring for calls of secondary users due to a missing permission check. | 7.8 |
2023-10-30 | CVE-2023-21379 | Out-of-bounds Read vulnerability in Google Android In Bluetooth, there is a possible out of bounds read due to a missing bounds check. | 4.4 |
2023-10-30 | CVE-2023-21380 | Out-of-bounds Write vulnerability in Google Android In Bluetooth, there is a possible out of bounds write due to a heap buffer overflow. | 6.7 |
2023-10-30 | CVE-2023-21381 | Use After Free vulnerability in Google Android In Media Resource Manager, there is a possible local arbitrary code execution due to use after free. | 7.8 |
2023-10-30 | CVE-2023-21382 | Missing Authorization vulnerability in Google Android In Content Resolver, there is a possible method to access metadata about existing content providers on the device due to a missing permission check. | 5.5 |