# CVE-2024-31755: Null dereference in n/a

> A segmentation violation in cJSON allows attackers to cause a denial of service via the cJSON_SetValuestring function.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** AZL-40184, AZL-67458, BELL-CVE-2024-31755, DEBIAN-CVE-2024-31755, GHSA-5g69-hr8r-x577, MGASA-2024-0324, RHSA-2025:9022, RHSA-2025:9203, UBUNTU-CVE-2024-31755, openSUSE-SU-2024:14021-1

## What is CVE-2024-31755?

CVE-2024-31755 is a high-severity vulnerability in n/a, published on 26 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2024-31755?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cjson` | Red Hat:satellite:6.16::el8 | All versions | 0:1.7.18-1.el8sat |
| `cjson-debuginfo` | Red Hat:satellite:6.16::el8 | All versions | 0:1.7.18-1.el8sat |
| `cjson-debugsource` | Red Hat:satellite:6.16::el8 | All versions | 0:1.7.18-1.el8sat |
| `cjson` | Red Hat:satellite:6.16::el9 | All versions | 0:1.7.18-1.el9sat |
| `cjson-debuginfo` | Red Hat:satellite:6.16::el9 | All versions | 0:1.7.18-1.el9sat |
| `cjson-debugsource` | Red Hat:satellite:6.16::el9 | All versions | 0:1.7.18-1.el9sat |
| `cjson` | Red Hat:satellite:6.17::el9 | All versions | 0:1.7.18-1.el9sat |
| `cjson-debuginfo` | Red Hat:satellite:6.17::el9 | All versions | 0:1.7.18-1.el9sat |
| `cjson-debugsource` | Red Hat:satellite:6.17::el9 | All versions | 0:1.7.18-1.el9sat |
| `cjson` | Red Hat:satellite_capsule:6.16::el8 | All versions | 0:1.7.18-1.el8sat |
| `cjson-debuginfo` | Red Hat:satellite_capsule:6.16::el8 | All versions | 0:1.7.18-1.el8sat |
| `cjson-debugsource` | Red Hat:satellite_capsule:6.16::el8 | All versions | 0:1.7.18-1.el8sat |
| `cjson` | Red Hat:satellite_capsule:6.16::el9 | All versions | 0:1.7.18-1.el9sat |
| `cjson-debuginfo` | Red Hat:satellite_capsule:6.16::el9 | All versions | 0:1.7.18-1.el9sat |
| `cjson-debugsource` | Red Hat:satellite_capsule:6.16::el9 | All versions | 0:1.7.18-1.el9sat |
| `cjson` | Red Hat:satellite_capsule:6.17::el9 | All versions | 0:1.7.18-1.el9sat |
| `cjson-debuginfo` | Red Hat:satellite_capsule:6.17::el9 | All versions | 0:1.7.18-1.el9sat |
| `cjson-debugsource` | Red Hat:satellite_capsule:6.17::el9 | All versions | 0:1.7.18-1.el9sat |
| `cJSON` | openSUSE:Tumbleweed | All versions | 1.7.18-1.1 |

Products: Cjson Project Cjson.

## How do I fix CVE-2024-31755?

Upgrade to a fixed version.

## Is CVE-2024-31755 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31755 exists.

## Other vulnerabilities in n/a

- [CVE-2023-53154](https://insights.sbomify.com/CVE-2023-53154/): Memory corruption in cJSON (low 2.9)
- [CVE-2023-26819](https://insights.sbomify.com/CVE-2023-26819/): Denial of service in cJSON (low 2.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-31755 and fix it if it is affected.

What it is: CVE-2024-31755 is a high-severity vulnerability in n/a, published on 26 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31755 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-31755/ (Markdown: https://insights.sbomify.com/CVE-2024-31755/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-31755
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-31755
- OSV: https://osv.dev/vulnerability/CVE-2024-31755

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-31755/
Summaries are generated and may contain mistakes; the official description above is the record.