Google

Android

8158 Schwachstellen gefunden.

Hinweis: Diese Liste kann unvollständig sein. Daten werden ohne Gewähr im Ursprungsformat bereitgestellt.
  • EPSS 0.1%
  • Veröffentlicht 30.03.2022 16:15:08
  • Zuletzt bearbeitet 21.11.2024 05:43:22

In createBluetoothDeviceSlice of ConnectedDevicesSliceProvider.java, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local escalation of privilege with no additional execution privileges needed. User interacti...

  • EPSS 0.1%
  • Veröffentlicht 30.03.2022 16:15:08
  • Zuletzt bearbeitet 21.11.2024 05:43:26

In createGeneralSlice of ConnectedDevicesSliceProvider.java.java, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not ne...

  • EPSS 0.1%
  • Veröffentlicht 30.03.2022 16:15:08
  • Zuletzt bearbeitet 21.11.2024 06:20:07

In ArrayMap, there is a possible leak of the content of SMS messages due to log information disclosure. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation.Product: ...

  • EPSS 0.11%
  • Veröffentlicht 16.03.2022 15:15:12
  • Zuletzt bearbeitet 21.11.2024 06:20:06

In the TitanM chip, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersi...

  • EPSS 0.11%
  • Veröffentlicht 16.03.2022 15:15:12
  • Zuletzt bearbeitet 21.11.2024 06:20:06

In TBD of TBD, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: An...

  • EPSS 0.11%
  • Veröffentlicht 16.03.2022 15:15:12
  • Zuletzt bearbeitet 21.11.2024 06:20:06

In ProtocolStkProactiveCommandAdapter::Init of protocolstkadapter.cpp, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interactio...

  • EPSS 0.11%
  • Veröffentlicht 16.03.2022 15:15:12
  • Zuletzt bearbeitet 21.11.2024 06:20:06

In copy_io_entries of lwis_ioctl.c, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.P...

  • EPSS 0.11%
  • Veröffentlicht 16.03.2022 15:15:12
  • Zuletzt bearbeitet 21.11.2024 06:20:06

In amcs_cdev_unlocked_ioctl of audiometrics.c, there is a possible out of bounds write due to improper input validation. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for expl...

  • EPSS 0.1%
  • Veröffentlicht 16.03.2022 15:15:12
  • Zuletzt bearbeitet 21.11.2024 06:20:07

In sendMessage of OneToOneChatImpl.java (? TBD), there is a possible way to send an RCS message without permissions due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. Us...

  • EPSS 0.09%
  • Veröffentlicht 16.03.2022 15:15:12
  • Zuletzt bearbeitet 21.11.2024 06:20:07

In gasket_alloc_coherent_memory of gasket_page_table.c, there is a possible memory corruption due to a race condition. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploi...