Vulnerabilities > Google > Android

DATE CVE VULNERABILITY TITLE RISK
2023-10-30 CVE-2023-21362 Unspecified vulnerability in Google Android
In Usage, there is a possible permanent DoS due to resource exhaustion.
local
low complexity
google
5.5
2023-10-30 CVE-2023-21364 Unspecified vulnerability in Google Android
In ContactsProvider, there is a possible crash loop due to resource exhaustion.
local
low complexity
google
5.5
2023-10-30 CVE-2023-21365 Unspecified vulnerability in Google Android
In Contacts, there is a possible crash loop due to resource exhaustion.
local
low complexity
google
5.5
2023-10-30 CVE-2023-21366 Unspecified vulnerability in Google Android
In Scudo, there is a possible way for an attacker to predict heap allocation patterns due to insecure implementation/design.
local
low complexity
google
5.5
2023-10-30 CVE-2023-21367 Unspecified vulnerability in Google Android
In Scudo, there is a possible way to exploit certain heap OOB read/write issues due to an insecure implementation/design.
local
low complexity
google
5.5
2023-10-30 CVE-2023-21368 Out-of-bounds Read vulnerability in Google Android
In Audio, there is a possible out of bounds read due to missing bounds check.
local
low complexity
google CWE-125
5.5
2023-10-30 CVE-2023-21369 Unspecified vulnerability in Google Android
In Usage Access, there is a possible way to display a Settings usage access restriction toggle screen due to a permissions bypass.
local
low complexity
google
5.5
2023-10-30 CVE-2023-21370 Integer Overflow or Wraparound vulnerability in Google Android
In the Security Element API, there is a possible out of bounds write due to an integer overflow.
local
low complexity
google CWE-190
6.7
2023-10-30 CVE-2023-21371 Integer Overflow or Wraparound vulnerability in Google Android
In Secure Element, there is a possible out of bounds write due to an integer overflow.
local
low complexity
google CWE-190
6.7
2023-10-27 CVE-2023-40116 Unspecified vulnerability in Google Android 11.0/12.0/12.1
In onTaskAppeared of PipTaskOrganizer.java, there is a possible way to bypass background activity launch restrictions due to a logic error in the code.
local
low complexity
google
7.8