Google

Android

8032 Schwachstellen gefunden.

Hinweis: Diese Liste kann unvollständig sein. Daten werden ohne Gewähr im Ursprungsformat bereitgestellt.
  • EPSS 0.02%
  • Veröffentlicht 12.08.2022 15:15:11
  • Zuletzt bearbeitet 21.11.2024 06:42:31

In Content, there is a possible way to learn about an account present on the device due to a missing permission check. This could lead to local information disclosure with User execution privileges needed. User interaction is not needed for exploitat...

  • EPSS 0.02%
  • Veröffentlicht 12.08.2022 15:15:11
  • Zuletzt bearbeitet 21.11.2024 06:42:32

In ContentService, there is a possible way to check if an account exists on the device due to a missing permission check. This could lead to local information disclosure with User execution privileges needed. User interaction is not needed for exploi...

  • EPSS 0.02%
  • Veröffentlicht 12.08.2022 15:15:11
  • Zuletzt bearbeitet 21.11.2024 06:42:32

In ContentService, there is a possible way to check if an account exists on the device due to a missing permission check. This could lead to local information disclosure with User execution privileges needed. User interaction is not needed for exploi...

  • EPSS 0.02%
  • Veröffentlicht 12.08.2022 15:15:11
  • Zuletzt bearbeitet 21.11.2024 06:42:32

In Settings, there is a possible way to bypass factory reset protections due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitatio...

  • EPSS 0.02%
  • Veröffentlicht 12.08.2022 15:15:11
  • Zuletzt bearbeitet 21.11.2024 06:42:32

In ContentService, there is a possible way to check if an account exists on the device due to a missing permission check. This could lead to local information disclosure with User execution privileges needed. User interaction is not needed for exploi...

  • EPSS 0.02%
  • Veröffentlicht 12.08.2022 15:15:11
  • Zuletzt bearbeitet 21.11.2024 06:42:32

In ContentService, there is a possible way to check if the given account exists on the device due to a missing permission check. This could lead to local information disclosure with User execution privileges needed. User interaction is not needed for...

  • EPSS 0.02%
  • Veröffentlicht 12.08.2022 15:15:11
  • Zuletzt bearbeitet 21.11.2024 06:42:32

In Content, there is a possible way to check if the given account exists on the device due to a missing permission check. This could lead to local information disclosure with User execution privileges needed. User interaction is not needed for exploi...

  • EPSS 0.02%
  • Veröffentlicht 12.08.2022 15:15:11
  • Zuletzt bearbeitet 21.11.2024 06:42:32

In Content, there is a possible way to check if an account exists on the device due to a missing permission check. This could lead to local information disclosure with User execution privileges needed. User interaction is not needed for exploitation....

  • EPSS 0.03%
  • Veröffentlicht 12.08.2022 15:15:11
  • Zuletzt bearbeitet 21.11.2024 06:42:32

In Settings, there is a possible way to bypass factory reset protections due to a sandbox escape. This could lead to local escalation of privilege if the attacker has physical access to the device, with no additional execution privileges needed. User...

  • EPSS 0.02%
  • Veröffentlicht 12.08.2022 15:15:11
  • Zuletzt bearbeitet 21.11.2024 06:42:33

In ContentService, there is a possible way to determine if an account is on the device without GET_ACCOUNTS permission due to a missing permission check. This could lead to local information disclosure with User execution privileges needed. User inte...