Android.

In Zen Mode, there is a possible permission bypass due to an unsafe PendingIntent.

• Android

In NotificationManagerService, there is a possible permission bypass due to an unsafe PendingIntent.

• Android

In InputManagerService, there is a possible permission bypass due to an unsafe PendingIntent.

• Android

In Settings, there is a possible permission bypass due to an unsafe PendingIntent.

• Android

In Settings, there is a possible permission bypass due to an unsafe PendingIntent.

• Android

In Settings, there is a possible permission bypass due to an unsafe PendingIntent.

• Android

In Settings, there is a possible permission bypass due to an unsafe PendingIntent.

• Android

In NFC, there is a possible out of bounds read due to uninitialized data.

• Android

In Telecom, there is a possible permission bypass due to an unsafe PendingIntent.

• Android

Android: In bindWallpaperComponentLocked of WallpaperManagerService.java…

• Android

In Bluetooth, there is a possible out of bounds read due to a missing bounds check.

• Android

In Bluetooth, there is a possible out of bounds read due to a missing bounds check.

• Android

In Bluetooth AVRCP, there is a possible leak of audio metadata due to residual data.

• Android

In Telephony, there is a possible permission bypass due to a missing permission check.

• Android

In Telephony, there is a possible permission bypass due to a missing permission check.

• Android

In NFC, there is a possible out of bounds read due to a missing bounds check.

• Android

In NFC, there is a possible out of bounds read due to a missing bounds check.

• Android

In Telephony, there is a possible permission bypass due to a missing permission check.

• Android

In libhwbinder, there is a possible information disclosure due to uninitialized data.

• Android

In Android Auto Settings, there is a possible permission bypass due to an unsafe PendingIntent.

• Android

In Telephony, there are possible leaks of sensitive data due to missing permission checks.

• Android

In the Accessibility service, there is a possible permission bypass due to an unsafe PendingIntent.

• Android

Android: In NetworkStackNotifier, there is a possible permissions bypass due to an unsafe implicit…

• Android

In NFC, there is a possible out of bounds write due to a missing bounds check.

• Android

In iptables, there is a possible out of bounds write due to an incorrect bounds check.

• Android

In NFC, there is a possible out of bounds write due to a missing bounds check.

• Android

In NFC, there is a possible out of bounds write due to a missing bounds check.

• Android

In NFC, there is a possible out of bounds write due to uninitialized data.

• Android

In NFC, there is a possible out of bounds write due to a missing bounds check.

• Android

In the Bluetooth server, there is a possible out of bounds write due to an integer overflow.

• Android

Android: In Bluetooth, there is a possible spoofing of bluetooth device metadata due to a missing…

• Android

Android: In Bluetooth, there is a possible control over Bluetooth enabled state due to a missing…

• Android

In hwservicemanager, there is a possible out of bounds write due to freeing a wild pointer.

• Android

In the Settings app, there is an insecure default value.

• Android

In NFC, there is a possible use-after-free due to a race condition.

• Android

In WiFi tethering, there is a possible attacker controlled intent due to an unsafe PendingIntent.

• Android

In the audio server, there is a missing permission check.

• Android

In Bluetooth, there is a possible out of bounds write due to a missing bounds check.

• Android

In the System UI, there is a possible system crash due to an uncaught exception.

• Android

In Telephony, there is a possible permission bypass due to a missing permission check.

• Android

In NFC, there is a possible permission bypass due to an unsafe PendingIntent.

• Android

In factory reset protection, there is a possible FRP bypass due to a missing permission check.

• Android

In libmedia, there is a possible resource exhaustion due to improper input validation.

• Android

In libstagefright, there is a possible resource exhaustion due to improper input validation.

• Android

In libmp4extractor, there is a possible resource exhaustion due to a missing bounds check.

• Android

In libstagefright, there is possible CPU exhaustion due to improper input validation.

• Android

In libstagefright, there is a possible dead loop due to an uncaught exception.

• Android

In libstagefright, there is a possible resource exhaustion due to improper input validation.

• Android

In libstagefright, there is a possible resource exhaustion due to improper input validation.

• Android

In libmkvextractor, there is a possible resource exhaustion due to a missing bounds check.

• Android

In SoundTriggerHwService, there is a possible out of bounds read due to a race condition.

• Android

In libAACdec, there is a possible out of bounds read due to missing bounds check.

• Android

In libDRCdec, there is a possible out of bounds read due to a missing bounds check.

• Android

In libDRCdec, there is a possible information disclosure due to uninitialized data.

• Android

In GLESRenderEngine, there is a possible out of bounds read due to a buffer overflow.

• Android

In libFraunhoferAAC, there is a possible out of bounds read due to a missing bounds check.

• Android

In MediaProvider, there is a possible permissions bypass due to SQL injection.

• Android

In libcodec2_soft_mp3dec, there is a possible information disclosure due to uninitialized data.

• Android

In the OMX encoder, there is a possible out of bounds read due to invalid input validation.

• Android

In the camera, there is a possible out of bounds read due to an integer overflow.

• Android