Vulnerabilities > NULL Pointer Dereference
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2023-04-13 | CVE-2022-25739 | NULL Pointer Dereference vulnerability in Qualcomm products Denial of service in modem due to missing null check while processing the ipv6 packet received during ECM call | 7.5 |
2023-04-13 | CVE-2022-33223 | NULL Pointer Dereference vulnerability in Qualcomm products Transient DOS in Modem due to null pointer dereference while processing the incoming packet with http chunked encoding. | 7.5 |
2023-04-13 | CVE-2022-33294 | NULL Pointer Dereference vulnerability in Qualcomm products Transient DOS in Modem due to NULL pointer dereference while receiving response of lwm2m registration/update/bootstrap request message. | 7.5 |
2023-04-11 | CVE-2022-47465 | NULL Pointer Dereference vulnerability in Google Android In vdsp service, there is a missing permission check. | 5.5 |
2023-04-11 | CVE-2022-47466 | NULL Pointer Dereference vulnerability in Google Android 10.0/11.0 In telecom service, there is a missing permission check. | 5.5 |
2023-04-11 | CVE-2022-47467 | NULL Pointer Dereference vulnerability in Google Android 10.0/11.0 In telecom service, there is a missing permission check. | 5.5 |
2023-04-11 | CVE-2022-47468 | NULL Pointer Dereference vulnerability in Google Android 10.0/11.0 In telecom service, there is a missing permission check. | 5.5 |
2023-04-11 | CVE-2023-26917 | NULL Pointer Dereference vulnerability in Cesnet Libyang libyang from v2.0.164 to v2.1.30 was discovered to contain a NULL pointer dereference via the function lysp_stmt_validate_value at lys_parse_mem.c. | 7.5 |
2023-04-04 | CVE-2020-23259 | NULL Pointer Dereference vulnerability in Jsish An issue found in Jsish v.3.0.11 and before allows an attacker to cause a denial of service via the Jsi_Strlen function in the src/jsiChar.c file. | 7.5 |
2023-04-03 | CVE-2023-26916 | NULL Pointer Dereference vulnerability in multiple products libyang from v2.0.164 to v2.1.30 was discovered to contain a NULL pointer dereference via the function lys_parse_mem at lys_parse_mem.c. | 5.3 |