Vulnerabilities > Google > Android > Medium
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2022-12-16 | CVE-2022-20553 | Improper Restriction of Rendered UI Layers or Frames vulnerability in Google Android 13.0 In onCreate of LogAccessDialogActivity.java, there is a possible way to bypass a permission check due to a tapjacking/overlay attack. | 6.5 |
2022-12-16 | CVE-2022-20554 | Use After Free vulnerability in Google Android 13.0 In removeEventHubDevice of InputDevice.cpp, there is a possible OOB read due to a use after free. | 6.7 |
2022-12-16 | CVE-2022-20555 | Out-of-bounds Read vulnerability in Google Android 13.0 In ufdt_get_node_by_path_len of ufdt_convert.c, there is a possible out of bounds read due to a missing bounds check. | 4.4 |
2022-12-16 | CVE-2022-20557 | Out-of-bounds Read vulnerability in Google Android 13.0 In MessageQueueBase of MessageQueueBase.h, there is a possible out of bounds read due to a missing bounds check. | 6.7 |
2022-12-16 | CVE-2022-20563 | Out-of-bounds Read vulnerability in Google Android In TBD of ufdt_convert, there is a possible out of bounds read due to memory corruption. | 6.7 |
2022-12-16 | CVE-2022-20564 | Out-of-bounds Write vulnerability in Google Android In _ufdt_output_strtab_to_fdt of ufdt_convert.c, there is a possible out of bounds write due to an incorrect bounds check. | 6.7 |
2022-12-16 | CVE-2022-20567 | Race Condition vulnerability in Google Android In pppol2tp_create of l2tp_ppp.c, there is a possible use after free due to a race condition. | 6.4 |
2022-12-16 | CVE-2022-20569 | Out-of-bounds Write vulnerability in Google Android In thermal_cooling_device_stats_update of thermal_sysfs.c, there is a possible out of bounds write due to improper input validation. | 6.7 |
2022-12-16 | CVE-2022-20570 | Unspecified vulnerability in Google Android Product: AndroidVersions: Android kernelAndroid ID: A-230660904References: N/A | 5.5 |
2022-12-16 | CVE-2022-20571 | Use After Free vulnerability in Google Android In extract_metadata of dm-android-verity.c, there is a possible way to corrupt kernel memory due to a use after free. | 6.7 |