Vulnerabilities > Google > Android > Medium
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2022-12-16 | CVE-2022-20588 | Improper Check for Unusual or Exceptional Conditions vulnerability in Google Android In sysmmu_map of sysmmu.c, there is a possible EoP due to a precondition check failure. | 6.7 |
| 2022-12-16 | CVE-2022-20589 | Improper Input Validation vulnerability in Google Android In valid_va_secbuf_check of drm_access_control.c, there is a possible ID due to improper input validation. | 4.4 |
| 2022-12-16 | CVE-2022-20590 | Improper Input Validation vulnerability in Google Android In valid_va_sec_mfc_check of drm_access_control.c, there is a possible information disclosure due to improper input validation. | 5.5 |
| 2022-12-16 | CVE-2022-20591 | Unspecified vulnerability in Google Android In ppmpu_set of ppmpu.c, there is a possible information disclosure due to a logic error in the code. | 5.5 |
| 2022-12-16 | CVE-2022-20592 | Improper Input Validation vulnerability in Google Android In ppmp_validate_secbuf of drm_fw.c, there is a possible information disclosure due to improper input validation. | 5.5 |
| 2022-12-16 | CVE-2022-20593 | Out-of-bounds Read vulnerability in Google Android In pop_descriptor_string of BufferDescriptor.h, there is a possible out of bounds read due to a missing bounds check. | 4.4 |
| 2022-12-16 | CVE-2022-20594 | Out-of-bounds Write vulnerability in Google Android In updateStart of WirelessCharger.cpp, there is a possible out of bounds write due to a missing bounds check. | 6.7 |
| 2022-12-16 | CVE-2022-20595 | Out-of-bounds Read vulnerability in Google Android In getWpcAuthChallengeResponse of WirelessCharger.cpp, there is a possible out of bounds read due to a missing bounds check. | 4.4 |
| 2022-12-16 | CVE-2022-20596 | Out-of-bounds Write vulnerability in Google Android In sendChunk of WirelessCharger.cpp, there is a possible out of bounds write due to a missing bounds check. | 6.7 |
| 2022-12-16 | CVE-2022-20599 | Unspecified vulnerability in Google Android In Pixel firmware, there is a possible exposure of sensitive memory due to a missing bounds check. | 6.7 |