# CVE-2023-23462: Libpeconv – integer overflow

> An integer overflow in Libpeconv allows attackers to cause denial of service or potentially execute code via crafted PE files.

- **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:** 15 Feb 2023
- **Updated:** 19 Mar 2025
- **Also known as:** GHSA-wmgh-44xh-27j6

## What is CVE-2023-23462?

CVE-2023-23462 is a critical vulnerability in Hasherezade (github) Libpeconv, published on 15 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Libpeconv – integer overflow, before commit 75b1565 (30/11/2022).

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Libpeconv Project Libpeconv.

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

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

## Is CVE-2023-23462 being exploited?

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

## Other vulnerabilities in Hasherezade (github) Libpeconv

- [CVE-2023-23461](https://insights.sbomify.com/CVE-2023-23461/): Libpeconv – access violation (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-23462 is a critical vulnerability in Hasherezade (github) Libpeconv, published on 15 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-23462 in the wild and no public exploit code.

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

## Sources

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

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