Vulnerabilities > Google > Android
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2023-07-04 | CVE-2023-20771 | Out-of-bounds Write vulnerability in Google Android 12.0 In display, there is a possible memory corruption due to a race condition. | 6.4 |
2023-07-04 | CVE-2023-20772 | Missing Authorization vulnerability in Google Android 12.0/13.0 In vow, there is a possible escalation of privilege due to a missing permission check. | 6.7 |
2023-07-04 | CVE-2023-20773 | Missing Authorization vulnerability in Google Android 12.0/13.0 In vow, there is a possible escalation of privilege due to a missing permission check. | 7.8 |
2023-07-04 | CVE-2023-20774 | Out-of-bounds Read vulnerability in Google Android 12.0/13.0 In display, there is a possible out of bounds read due to a missing bounds check. | 6.7 |
2023-07-04 | CVE-2023-20775 | Out-of-bounds Write vulnerability in multiple products In display, there is a possible out of bounds write due to a missing bounds check. | 6.7 |
2023-06-28 | CVE-2022-20443 | Improper Restriction of Rendered UI Layers or Frames vulnerability in Google Android 13.0 In hasInputInfo of Layer.cpp, there is a possible bypass of user interaction requirements due to a tapjacking/overlay attack. | 7.8 |
2023-06-28 | CVE-2023-21066 | Out-of-bounds Write vulnerability in Google Android In cd_CodeMsg of cd_codec.c, there is a possible out of bounds write due to a heap buffer overflow. | 9.8 |
2023-06-28 | CVE-2023-21146 | Use After Free vulnerability in Google Android there is a possible way to corrupt memory due to a use after free. | 6.7 |
2023-06-28 | CVE-2023-21147 | Use After Free vulnerability in Google Android In lwis_i2c_device_disable of lwis_device_i2c.c, there is a possible UAF due to a logic error in the code. | 7.8 |
2023-06-28 | CVE-2023-21148 | Out-of-bounds Read vulnerability in Google Android In BuildSetConfig of protocolimsbuilder.cpp, there is a possible out of bounds read due to a missing null check. | 4.4 |