Platform
Android
6,319 known vulnerabilities.
6,319 results · Feed
-
Unscored —
In parseExclusiveStateAnnotation of LogEvent.cpp, there is a possible out of bounds write due to a heap buffer overflow…
-
Unscored —
In parsePrimaryFieldFirstUidAnnotation of LogEvent.cpp, there is a possible out of bounds write due to a heap buffer ov…
-
Unscored —
In setPowerModeWithHandle of com_android_server_power_PowerManagerService.cpp, there is a possible out of bounds write …
-
Unscored —CVE-2021-0435 Public exploit
In avrc_proc_vendor_command of avrc_api.cc, there is a possible leak of heap data due to uninitialized data. This could…
-
Unscored —CVE-2021-0431 Public exploit
In avrc_msg_cback of avrc_api.cc, there is a possible out of bounds read due to a missing bounds check. This could lead…
-
Unscored —
In ClearPullerCacheIfNecessary and ForceClearPullerCache of StatsPullerManager.cpp, there is a possible use-after-free …
-
Unscored —
In getSimSerialNumber of TelephonyManager.java, there is a possible way to read a trackable identifier due to a missing…
-
Unscored —
In start of WelcomeActivity.java, there is a possible residual profile due to a confused deputy. This could lead to loc…
-
Unscored —
In ImportVCardActivity, there is a possible way to bypass user consent due to a tapjacking/overlay attack. This could l…
-
Unscored —CVE-2021-0433 Public exploit
In onCreate of DeviceChooserActivity.java, there is a possible way to bypass user consent when pairing a Bluetooth devi…
-
Unscored —
In several functions of ScreenshotHelper.java and related files, there is a possible incorrectly saved screenshot due t…
-
Unscored —
In several functions of InputDispatcher.cpp, WindowManagerService.java, and related files, there is a possible tapjacki…
-
Unscored —CVE-2021-24027 Public exploit
A cache configuration issue prior to WhatsApp for Android v2.21.4.18 and WhatsApp Business for Android v2.21.4.18 may h…
-
Unscored —
A missing bounds check within the audio decoding pipeline for WhatsApp calls in WhatsApp for Android prior to v2.21.3, …
-
Unscored —
In GenerateFaceMask of face.cc, there is a possible out of bounds write due to an incorrect bounds check. This could le…
-
Unscored —
In sound_trigger_event_alloc of platform.h, there is a possible out of bounds write due to a heap buffer overflow. This…
-
Unscored —
In convertToHidl of convert.cpp, there is a possible out of bounds read due to uninitialized data from ReturnFrameworkM…
-
Unscored —
In the NXP NFC firmware, there is a possible insecure firmware update due to a logic error. This could lead to local es…
-
Unscored —
In iaxxx_core_sensor_change_state of iaxxx-module.c, there is a possible out of bounds write due to a missing bounds ch…
-
Unscored —
In the FingerTipS touch screen driver, there is a possible out of bounds read due to an integer overflow. This could le…
-
Unscored —
In fts_driver_test_write of fts_proc.c, there is a possible out of bounds read due to a missing bounds check. This coul…
-
Unscored —
In the FingerTipS touch screen driver, there is a possible out of bounds read due to an integer overflow. This could le…
-
Unscored —
In the FingerTipS touch screen driver, there is a possible out of bounds write due to a heap buffer overflow. This coul…
-
Unscored —
In the Citadel chip firmware, there is a possible out of bounds write due to a missing bounds check. This could lead to…
-
Unscored —
In the Citadel chip firmware, there is a possible out of bounds write due to a missing bounds check. This could lead to…
-
Unscored —
In the Citadel chip firmware, there is a possible out of bounds write due to a missing bounds check. This could lead to…
-
Unscored —
In the Titan-M chip firmware, there is a possible disclosure of stack memory due to uninitialized data. This could lead…
-
Unscored —
In the Titan M chip firmware, there is a possible disclosure of stack memory due to uninitialized data. This could lead…
-
Unscored —
In the Titan M chip firmware, there is a possible disclosure of stack memory due to uninitialized data. This could lead…
-
Unscored —
In the Titan M chip firmware, there is a possible disclosure of stack memory due to uninitialized data. This could lead…
-
Unscored —
In the Titan M chip firmware, there is a possible disclosure of stack memory due to uninitialized data. This could lead…
-
Unscored —
In setNightModeActivated of UiModeManagerService.java, there is a missing permission check. This could lead to local es…
-
Unscored —
In onReceive of ImsPhoneCallTracker.java, there is a possible misattribution of data usage due to an incorrect broadcas…
-
Unscored —
In FindQuotaDeviceForUuid of QuotaUtils.cpp, there is a possible use-after-free due to a race condition. This could lea…
-
Unscored —
In onCreate of UsbConfirmActivity, there is a possible tapjacking vector due to an insecure default value. This could l…
-
Unscored —
In createConnectToAvailableNetworkNotification of ConnectToNetworkNotificationBuilder.java, there is a possible connect…
-
Unscored —
In done of CaptivePortalLoginActivity.java, there is a confused deputy. This could lead to local escalation of privileg…
-
Unscored —
In checkSlicePermission of SliceManagerService.java, there is a possible resource exposure due to an incorrect permissi…
-
Unscored —
In updateNotifications of DeviceStorageMonitorService.java, there is a possible permission bypass due to an unsafe Pend…
-
Unscored —
In onReceive of DcTracker.java, there is a possible way to trigger a provisioning URL and modify other telephony settin…