Google

Android

8032 Schwachstellen gefunden.

Hinweis: Diese Liste kann unvollständig sein. Daten werden ohne Gewähr im Ursprungsformat bereitgestellt.
  • EPSS 2.16%
  • Veröffentlicht 21.06.2021 17:15:08
  • Zuletzt bearbeitet 21.11.2024 05:42:51

In ConnectionHandler::SdpCb of connection_handler.cc, there is a possible out of bounds read due to a use after free. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for ...

  • EPSS 0.01%
  • Veröffentlicht 21.06.2021 17:15:08
  • Zuletzt bearbeitet 21.11.2024 05:42:51

In onCreate of WifiScanModeActivity.java, there is a possible way to enable Wi-Fi scanning without user consent due to a tapjacking/overlay attack. This could lead to local escalation of privilege with User execution privileges needed. User interacti...

  • EPSS 0.02%
  • Veröffentlicht 21.06.2021 17:15:08
  • Zuletzt bearbeitet 21.11.2024 05:42:52

In memory management driver, there is a possible out of bounds write 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: An...

  • EPSS 0.02%
  • Veröffentlicht 21.06.2021 17:15:08
  • Zuletzt bearbeitet 21.11.2024 05:42:52

In memory management driver, there is a possible out of bounds write due to uninitialized data. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: ...

  • EPSS 0.02%
  • Veröffentlicht 21.06.2021 17:15:08
  • Zuletzt bearbeitet 21.11.2024 05:42:52

In memory management driver, there is a 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: Andr...

  • EPSS 0.02%
  • Veröffentlicht 21.06.2021 17:15:08
  • Zuletzt bearbeitet 21.11.2024 05:42:52

In memory management driver, there is a possible memory corruption due to a double 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 0.01%
  • Veröffentlicht 21.06.2021 17:15:08
  • Zuletzt bearbeitet 21.11.2024 05:42:52

In memory management driver, there is a possible memory corruption due to improper locking. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: Andr...

  • EPSS 0.02%
  • Veröffentlicht 21.06.2021 17:15:08
  • Zuletzt bearbeitet 21.11.2024 05:42:52

In memory management driver, there is a possible out of bounds write due to uninitialized data. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: ...

  • EPSS 0.02%
  • Veröffentlicht 21.06.2021 17:15:08
  • Zuletzt bearbeitet 21.11.2024 05:42:52

In memory management driver, there is a 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: Andr...

  • EPSS 0.17%
  • Veröffentlicht 14.06.2021 20:15:07
  • Zuletzt bearbeitet 21.11.2024 05:42:30

Product: AndroidVersions: Android SoCAndroid ID: A-175402462