# CVE-2023-29418: Memory corruption in n/a

> An out-of-bounds read in the bzip3 library allows attackers to cause denial of service or disclose sensitive memory contents.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Apr 2023
- **Updated:** 5 Mar 2025
- **Also known as:** DEBIAN-CVE-2023-29418, GHSA-q597-3v27-cmvx, UBUNTU-CVE-2023-29418

## What is CVE-2023-29418?

CVE-2023-29418 is a medium-severity memory corruption vulnerability in n/a, published on 6 Apr 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in libbzip3.a in bzip3 before 1.2.3. There is an xwrite out-of-bounds read.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Bzip3 Project Bzip3.

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

Upgrade to a fixed version.

## Is CVE-2023-29418 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-29421](https://insights.sbomify.com/CVE-2023-29421/): Memory corruption in n/a (high 8.8)
- [CVE-2023-29415](https://insights.sbomify.com/CVE-2023-29415/): Denial of service in n/a (medium 6.5)
- [CVE-2023-29416](https://insights.sbomify.com/CVE-2023-29416/): Memory corruption in n/a (medium 6.5)
- [CVE-2023-29417](https://insights.sbomify.com/CVE-2023-29417/): Memory corruption in n/a (medium 6.5)
- [CVE-2023-29419](https://insights.sbomify.com/CVE-2023-29419/): Memory corruption in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-29418 is a medium-severity memory corruption vulnerability in n/a, published on 6 Apr 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-29418 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-29418/ (Markdown: https://insights.sbomify.com/CVE-2023-29418/index.md)
```

## Sources

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

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