# CVE-2023-1010: vox2png vox2png.c heap-based overflow

> A heap-based buffer overflow in vox2png allows local attackers to execute arbitrary code or cause denial of service.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Feb 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-vqp6-3hff-2h3w

## What is CVE-2023-1010?

CVE-2023-1010 is a medium-severity memory corruption vulnerability in vox2png, published on 24 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as critical was found in vox2png 1.0. Affected by this vulnerability is an unknown functionality of the file vox2png.c. The manipulation leads to heap-based buffer overflow. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-221743.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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

It affects 1 product.


Products: Vox2png Project Vox2png.

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

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

## Is CVE-2023-1010 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-1010 is a medium-severity memory corruption vulnerability in vox2png, published on 24 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-1010 exists.

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

## Sources

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

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