# CVE-2021-45423: Memory corruption in n/a

> A buffer overflow in the Pev binary analysis tool allows arbitrary code execution via a crafted PE file due to incorrect array bounds checking.

- **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:** Yes
- **Published:** 13 Mar 2023
- **Updated:** 3 Mar 2025
- **Also known as:** DEBIAN-CVE-2021-45423, GHSA-4r8p-6r2m-cjwv, UBUNTU-CVE-2021-45423

## What is CVE-2021-45423?

CVE-2021-45423 is a critical memory corruption vulnerability in n/a, published on 13 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Buffer Overflow vulnerabilityexists in Pev 0.81 via the pe_exports function from exports.c.. The array offsets_to_Names is dynamically allocated on the stack using exp->NumberOfFunctions as its size. However, the loop uses exp->NumberOfNames to iterate over it and set its components value. Therefore, the loop code assumes that exp->NumberOfFunctions is greater than ordinal at each iteration. This can lead to arbitrary code execution.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2021-45423?

It affects 1 product.


Products: Pev Project Pev.

## How do I fix CVE-2021-45423?

Apply the vendor's patch.

## Is CVE-2021-45423 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-45423 and fix it if it is affected.

What it is: CVE-2021-45423 is a critical memory corruption vulnerability in n/a, published on 13 Mar 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-2021-45423 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-2021-45423/ (Markdown: https://insights.sbomify.com/CVE-2021-45423/index.md)
```

## Sources

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

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