Vulnerabilities > Google > Android > Medium
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2022-12-16 | CVE-2022-42517 | Out-of-bounds Read vulnerability in Google Android In MiscService::DoOemSetTcsFci of miscservice.cpp, there is a possible out of bounds read due to a missing bounds check. | 4.4 |
| 2022-12-16 | CVE-2022-42518 | Out-of-bounds Write vulnerability in Google Android In BroadcastSmsConfigsRequestData::encode of smsdata.cpp, there is a possible out of bounds write due to a missing bounds check. | 6.7 |
| 2022-12-16 | CVE-2022-42519 | Out-of-bounds Write vulnerability in Google Android In CdmaBroadcastSmsConfigsRequestData::encode of cdmasmsdata.cpp, there is a possible stack clash leading to memory corruption. | 6.7 |
| 2022-12-16 | CVE-2022-42520 | Use After Free vulnerability in Google Android In ServiceInterface::HandleRequest of serviceinterface.cpp, there is a possible use after free. | 6.7 |
| 2022-12-16 | CVE-2022-42521 | Out-of-bounds Write vulnerability in Google Android In encode of wlandata.cpp, there is a possible out of bounds write due to improper input validation. | 6.7 |
| 2022-12-16 | CVE-2022-42522 | Out-of-bounds Read vulnerability in Google Android In DoSetCarrierConfig of miscservice.cpp, there is a possible out of bounds read due to an incorrect bounds check. | 4.4 |
| 2022-12-16 | CVE-2022-42523 | Out-of-bounds Write vulnerability in Google Android In fillSetupDataCallInfo_V1_6 of ril_service_1_6.cpp, there is a possible out of bounds write due to an incorrect bounds check. | 6.7 |
| 2022-12-16 | CVE-2022-42525 | Out-of-bounds Write vulnerability in Google Android In fillSetupDataCallInfo_V1_6 of ril_service_1_6.cpp, there is a possible out of bounds write due to an incorrect bounds check. | 6.7 |
| 2022-12-16 | CVE-2022-42526 | Out-of-bounds Write vulnerability in Google Android In ConvertUtf8ToUcs2 of radio_hal_utils.cpp, there is a possible out of bounds write due to a missing bounds check. | 6.7 |
| 2022-12-16 | CVE-2022-42530 | Out-of-bounds Read vulnerability in Google Android In Pixel firmware, there is a possible out of bounds read due to a missing bounds check. | 4.4 |