Vulnerabilities > Google > Android
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2023-03-24 | CVE-2023-21024 | Unspecified vulnerability in Google Android 13.0 In maybeFinish of FallbackHome.java, there is a possible delay of lockdown screen due to logic error. | 7.8 |
2023-03-24 | CVE-2023-21025 | Out-of-bounds Read vulnerability in Google Android 13.0 In ufdt_local_fixup_prop of ufdt_overlay.c, there is a possible out of bounds read due to an incorrect bounds check. | 4.4 |
2023-03-24 | CVE-2023-21026 | Unspecified vulnerability in Google Android 13.0 In updateInputChannel of WindowManagerService.java, there is a possible way to set a touchable region beyond its own SurfaceControl due to a logic error in the code. | 5.5 |
2023-03-24 | CVE-2023-21027 | Unspecified vulnerability in Google Android 13.0 In multiple functions of PasspointXmlUtils.java, there is a possible authentication misconfiguration due to a logic error in the code. | 7.5 |
2023-03-24 | CVE-2023-21028 | Out-of-bounds Read vulnerability in Google Android 13.0 In parse_printerAttributes of ipphelper.c, there is a possible out of bounds read due to a string without a null-terminator. | 7.5 |
2023-03-24 | CVE-2023-21029 | Missing Authorization vulnerability in Google Android 13.0 In register of UidObserverController.java, there is a missing permission check. | 5.5 |
2023-03-24 | CVE-2023-21030 | Double Free vulnerability in Google Android 13.0 In Confirmation of keystore_cli_v2.cpp, there is a possible way to corrupt memory due to a double free. | 7.8 |
2023-03-24 | CVE-2023-21031 | Out-of-bounds Read vulnerability in Google Android 13.0 In setPowerMode of HWC2.cpp, there is a possible out of bounds read due to a race condition. | 4.7 |
2023-03-24 | CVE-2023-21032 | Out-of-bounds Read vulnerability in Google Android 13.0 In _ufdt_output_node_to_fdt of ufdt_convert.c, there is a possible out of bounds read due to a heap buffer overflow. | 4.4 |
2023-03-24 | CVE-2023-21033 | Resource Exhaustion vulnerability in Google Android 13.0 In addNetwork of WifiManager.java, there is a possible way to trigger a persistent DoS due to resource exhaustion. | 5.5 |