Google

Android

7931 Schwachstellen gefunden.

Hinweis: Diese Liste kann unvollständig sein. Daten werden ohne Gewähr im Ursprungsformat bereitgestellt.
  • EPSS 0.03%
  • Veröffentlicht 13.04.2021 19:15:13
  • Zuletzt bearbeitet 21.11.2024 05:42:46

In LK, there is a possible escalation of privilege due to an insecure default value. This could lead to local escalation of privilege for an attacker who has physical access to the device with no additional execution privileges needed. User interacti...

  • EPSS 0.03%
  • Veröffentlicht 13.04.2021 19:15:13
  • Zuletzt bearbeitet 21.11.2024 05:42:46

In decrypt_1_2 of CryptoPlugin.cpp, there is a possible out of bounds read due to an integer overflow. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Pro...

  • EPSS 0.03%
  • Veröffentlicht 13.04.2021 19:15:12
  • Zuletzt bearbeitet 21.11.2024 05:42:39

In injectBestLocation and handleUpdateLocation of GnssLocationProvider.java, there is a possible incorrect reporting of location data to emergency services due to improper input validation. This could lead to incorrect reporting of location data to e...

  • EPSS 0.02%
  • Veröffentlicht 13.04.2021 19:15:12
  • Zuletzt bearbeitet 21.11.2024 05:42:42

In parsePrimaryFieldFirstUidAnnotation of LogEvent.cpp, there is a possible out of bounds write due to a heap buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not ne...

  • EPSS 0.02%
  • Veröffentlicht 13.04.2021 19:15:12
  • Zuletzt bearbeitet 21.11.2024 05:42:42

In parseExclusiveStateAnnotation of LogEvent.cpp, there is a possible out of bounds write due to a heap buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed f...

  • EPSS 0.02%
  • Veröffentlicht 13.04.2021 19:15:12
  • Zuletzt bearbeitet 21.11.2024 05:42:42

In getSimSerialNumber of TelephonyManager.java, there is a possible way to read a trackable identifier due to a missing permission check. This could lead to local information disclosure with User execution privileges needed. User interaction is not n...

  • EPSS 0.03%
  • Veröffentlicht 13.04.2021 19:15:12
  • Zuletzt bearbeitet 21.11.2024 05:42:42

In pollOnce of ALooper.cpp, there is possible memory corruption due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: Android...

  • EPSS 1.49%
  • Veröffentlicht 13.04.2021 19:15:12
  • Zuletzt bearbeitet 21.11.2024 05:42:42

In rw_mfc_handle_read_op of rw_mfc.cc, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution via a malicious NFC packet with no additional execution privileges needed. User interaction is not ...

  • EPSS 1.56%
  • Veröffentlicht 13.04.2021 19:15:12
  • Zuletzt bearbeitet 21.11.2024 05:42:42

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 to remote information disclosure to a paired device with no additional execution privileges needed. User interaction is not needed...

  • EPSS 0.01%
  • Veröffentlicht 13.04.2021 19:15:12
  • Zuletzt bearbeitet 21.11.2024 05:42:42

In ClearPullerCacheIfNecessary and ForceClearPullerCache of StatsPullerManager.cpp, there is a possible use-after-free due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User inte...