Vulnerabilities > Google > Android > High
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2024-09-13 | CVE-2024-44094 | Out-of-bounds Write vulnerability in Google Android In ppmp_protect_mfcfw_buf of code/drm_fw.c, there is a possible memory corruption due to improper input validation. | 7.8 |
2024-09-13 | CVE-2024-44095 | Out-of-bounds Write vulnerability in Google Android In ppmp_protect_mfcfw_buf of code/drm_fw.c, there is a possible corrupt memory due to a logic error in the code. | 7.8 |
2024-09-02 | CVE-2024-20089 | Improper Check for Unusual or Exceptional Conditions vulnerability in multiple products In wlan, there is a possible denial of service due to incorrect error handling. | 7.5 |
2024-08-19 | CVE-2024-32927 | Use After Free vulnerability in Google Android In sendDeviceState_1_6 of RadioExt.cpp, there is a possible use after free due to improper locking. | 7.8 |
2024-08-15 | CVE-2024-34727 | Classic Buffer Overflow vulnerability in Google Android In sdpu_compare_uuid_with_attr of sdp_utils.cc, there is a possible out of bounds read due to a heap buffer overflow. | 7.5 |
2024-06-13 | CVE-2024-29781 | Out-of-bounds Read vulnerability in Google Android In ss_AnalyzeOssReturnResUssdArgIe of ss_OssAsnManagement.c, there is a possible out of bounds read due to improper input validation. | 7.5 |
2024-06-13 | CVE-2024-29784 | Integer Overflow or Wraparound vulnerability in Google Android In prepare_response of lwis_periodic_io.c, there is a possible out of bounds write due to an integer overflow. | 7.8 |
2024-06-13 | CVE-2024-29787 | Use After Free vulnerability in Google Android In lwis_process_transactions_in_queue of lwis_transaction.c, there is a possible use after free due to a use after free. | 7.8 |
2024-06-13 | CVE-2024-32891 | Race Condition vulnerability in Google Android In sec_media_unprotect of media.c, there is a possible memory corruption due to a race condition. | 7.0 |
2024-06-13 | CVE-2024-32892 | Type Confusion vulnerability in Google Android In handle_init of goodix/main/main.c, there is a possible memory corruption due to type confusion. | 7.8 |