# CVE-2023-39125: Integer overflow in n/a

> An integer overflow in the NTSC-CRT library allows out-of-bounds writes when processing malformed BMP files, potentially leading to code execution or crashes.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 17 Aug 2023
- **Updated:** 8 Oct 2024
- **Also known as:** GHSA-gj46-f2mj-gph9

## What is CVE-2023-39125?

CVE-2023-39125 is a high-severity vulnerability in n/a, published on 17 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NTSC-CRT 2.2.1 has an integer overflow and out-of-bounds write in loadBMP in bmp_rw.c because a file's width, height, and BPP are not validated. NOTE: the vendor's perspective is "this main application was not intended to be a well tested program, it's just something to demonstrate it works and for the user to see how to integrate it into their own programs."

Weakness: CWE-787 (Out-of-bounds Write), CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Ntsc-Crt Project Ntsc-Crt.

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

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

## Is CVE-2023-39125 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-39125 is a high-severity vulnerability in n/a, published on 17 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-39125 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-2023-39125/ (Markdown: https://insights.sbomify.com/CVE-2023-39125/index.md)
```

## Sources

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

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