Vulnerabilities > Google > Android > 2.2.3

DATE CVE VULNERABILITY TITLE RISK
2023-10-30 CVE-2023-21392 Use After Free vulnerability in Google Android
In Bluetooth, there is a possible way to corrupt memory due to a use after free.
low complexity
google CWE-416
8.8
2023-10-30 CVE-2023-21393 Missing Authorization vulnerability in Google Android
In Settings, there is a possible way for the user to change SIM due to a missing permission check.
local
low complexity
google CWE-862
7.8
2023-10-30 CVE-2023-21394 Unspecified vulnerability in Google Android
In registerPhoneAccount of TelecomServiceImpl.java, there is a possible way to reveal images from another user due to a missing permission check.
local
low complexity
google
5.5
2023-10-30 CVE-2023-21395 Use After Free vulnerability in Google Android
In Bluetooth, there is a possible out of bounds read due to a use after free.
low complexity
google CWE-416
6.5
2023-10-30 CVE-2023-21396 Unspecified vulnerability in Google Android
In Activity Manager, there is a possible background activity launch due to a logic error in the code.
local
low complexity
google
7.8
2023-10-30 CVE-2023-21397 Unspecified vulnerability in Google Android
In Setup Wizard, there is a possible way to save a WiFi network due to an insecure default value.
local
low complexity
google
7.8
2023-10-30 CVE-2023-21398 Unspecified vulnerability in Google Android
In sdksandbox, there is a possible strandhogg style overlay attack due to a logic error in the code.
local
low complexity
google
7.8
2023-10-30 CVE-2023-40101 Out-of-bounds Read vulnerability in Google Android
In collapse of canonicalize_md.c, there is a possible out of bounds read due to a missing bounds check.
local
low complexity
google CWE-125
5.5
2023-10-30 CVE-2023-45780 Unspecified vulnerability in Google Android
In Print Service, there is a possible background activity launch due to a logic error in the code.
local
low complexity
google
7.3
2023-10-30 CVE-2021-39810 Missing Authorization vulnerability in Google Android
In NFC, there is a possible way to setup a default contactless payment app without user consent due to a missing permission check.
local
low complexity
google CWE-862
7.8