Google

Android

7931 Schwachstellen gefunden.

Hinweis: Diese Liste kann unvollständig sein. Daten werden ohne Gewähr im Ursprungsformat bereitgestellt.
  • EPSS 0.01%
  • Veröffentlicht 13.12.2022 16:15:17
  • Zuletzt bearbeitet 22.04.2025 18:15:46

In deletePackageVersionedInternal of DeletePackageHelper.java, there is a possible way to bypass carrier restrictions due to a permissions bypass. This could lead to local escalation of privilege with no additional execution privileges needed. User i...

  • EPSS 50.88%
  • Veröffentlicht 13.12.2022 16:15:16
  • Zuletzt bearbeitet 22.04.2025 15:15:58

In toLanguageTag of LocaleListCache.cpp, there is a possible out of bounds read due to an incorrect bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation...

  • EPSS 0.32%
  • Veröffentlicht 13.12.2022 16:15:16
  • Zuletzt bearbeitet 22.04.2025 15:15:58

In readLazyValue of Parcel.java, there is a possible loading of arbitrary code into the System Settings app due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is...

  • EPSS 0.01%
  • Veröffentlicht 13.12.2022 16:15:16
  • Zuletzt bearbeitet 22.04.2025 15:15:58

In test of ResetTargetTaskHelper.java, there is a possible hijacking of any app which sets allowTaskReparenting="true" due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User int...

  • EPSS 0.03%
  • Veröffentlicht 13.12.2022 16:15:16
  • Zuletzt bearbeitet 22.04.2025 18:15:44

In setEnabledSetting of PackageManager.java, there is a possible way to get the device into an infinite reboot loop due to resource exhaustion. This could lead to local denial of service with no additional execution privileges needed. User interactio...

  • EPSS 0.02%
  • Veröffentlicht 13.12.2022 16:15:16
  • Zuletzt bearbeitet 22.04.2025 18:15:45

In shouldHideNotification of KeyguardNotificationVisibilityProvider.kt, there is a possible way to show hidden notifications due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges ne...

  • EPSS 0.03%
  • Veröffentlicht 13.12.2022 16:15:16
  • Zuletzt bearbeitet 22.04.2025 18:15:46

In NotificationChannel of NotificationChannel.java, there is a possible failure to persist permissions settings due to resource exhaustion. This could lead to local escalation of privilege with no additional execution privileges needed. User interact...

  • EPSS 0.01%
  • Veröffentlicht 13.12.2022 16:15:16
  • Zuletzt bearbeitet 22.04.2025 18:15:46

In NotificationChannel of NotificationChannel.java, there is a possible failure to persist permissions settings due to resource exhaustion. This could lead to local escalation of privilege with no additional execution privileges needed. User interact...

  • EPSS 0.01%
  • Veröffentlicht 13.12.2022 16:15:16
  • Zuletzt bearbeitet 22.04.2025 20:15:20

In NotificationChannel of NotificationChannel.java, there is a possible failure to persist permissions settings due to resource exhaustion. This could lead to local escalation of privilege with no additional execution privileges needed. User interact...

  • EPSS 0.01%
  • Veröffentlicht 13.12.2022 16:15:16
  • Zuletzt bearbeitet 22.04.2025 20:15:20

In createNotificationChannel of NotificationManager.java, there is a possible way to make the device unusable and require factory reset due to resource exhaustion. This could lead to local denial of service with no additional execution privileges nee...