CVE-2024-31755: cJSON · NULL Pointer Dereference
Affects cJSONSource CVE Database V5
Not known to be exploited · CVSS 7.6 High.
Data as of 26 Oct 2026, 11:07 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubdavegamble/cJSONpkg:github/davegamble/cJSONOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-31755, organizations should first monitor for updates or patches from the cJSON maintainers and apply them promptly once available. In the interim, developers should implement strict input validation and sanitization on all JSON data before passing it to cJSON_SetValuestring or related functions to prevent null pointer dereferences. Employing memory-safe wrappers or runtime protections such as AddressSanitizer during development can help detect and prevent exploitation. Restrict network access to services using vulnerable cJSON versions to trusted sources only, reducing exposure to remote attacks. Additionally, implement robust error handling to gracefully manage unexpected input and avoid crashes. Security teams should monitor logs and system behavior for signs of abnormal crashes or exploitation attempts. Where feasible, consider replacing cJSON with alternative, actively maintained JSON libraries with stronger security track records. Finally, conduct thorough code reviews and fuzz testing focused on JSON parsing components to uncover and remediate similar vulnerabilities proactively.
Description
cJSON v1.7.17 was discovered to contain a segmentation violation, which can trigger through the second parameter of function cJSON_SetValuestring at cJSON.c.