Vulnerabilities > Google > Android > Medium
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 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 |
| 2022-12-16 | CVE-2022-20572 | Missing Authorization vulnerability in Google Android In verity_target of dm-verity-target.c, there is a possible way to modify read-only files due to a missing permission check. | 6.7 |
| 2022-12-16 | CVE-2022-20574 | Out-of-bounds Read vulnerability in Google Android In sec_sysmmu_info of drm_fw.c, there is a possible out of bounds read due to improper input validation. | 5.5 |
| 2022-12-16 | CVE-2022-20575 | Out-of-bounds Read vulnerability in Google Android In read_ppmpu_info of drm_fw.c, there is a possible out of bounds read due to an incorrect bounds check. | 5.5 |
| 2022-12-16 | CVE-2022-20576 | Out-of-bounds Write vulnerability in Google Android In externalOnRequest of rilapplication.cpp, there is a possible out of bounds write due to a missing bounds check. | 6.7 |
| 2022-12-16 | CVE-2022-20577 | Out-of-bounds Write vulnerability in Google Android In OemSimAuthRequest::encode of wlandata.cpp, there is a possible out of bounds write due to a missing bounds check. | 6.7 |
| 2022-12-16 | CVE-2022-20578 | Out-of-bounds Write vulnerability in Google Android In RadioImpl::setGsmBroadcastConfig of ril_service_legacy.cpp, there is a possible stack clash leading to memory corruption. | 6.7 |
| 2022-12-16 | CVE-2022-20579 | Out-of-bounds Write vulnerability in Google Android In RadioImpl::setCdmaBroadcastConfig of ril_service_legacy.cpp, there is a possible stack clash leading to memory corruption. | 6.7 |
| 2022-12-16 | CVE-2022-20580 | Out-of-bounds Write vulnerability in Google Android In ufdt_do_one_fixup of ufdt_overlay.c, there is a possible out of bounds write due to an incorrect bounds check. | 6.7 |