# CVE-2023-23087: Null dereference in n/a

> Attackers can execute arbitrary code or cause denial of service via a null pointer dereference in the destroy function of MojoJson.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2023
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-5gqm-qpgc-v969

## What is CVE-2023-23087?

CVE-2023-23087 is a critical vulnerability in n/a, published on 3 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was found in MojoJson v1.2.3 allows attackers to execute arbitary code via the destroy function.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2023-23087?

It affects 1 product.


Products: Mojojson Project Mojojson.

## How do I fix CVE-2023-23087?

No fix has been published for CVE-2023-23087 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-23087 being exploited?

There is no known exploitation of CVE-2023-23087 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-23086](https://insights.sbomify.com/CVE-2023-23086/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-23087 and fix it if it is affected.

What it is: CVE-2023-23087 is a critical vulnerability in n/a, published on 3 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-23087 in the wild and no public exploit code.

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-2023-23087/ (Markdown: https://insights.sbomify.com/CVE-2023-23087/index.md)
```

## Sources

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

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