# CVE-2023-52169: Information disclosure in n/a

> An out-of-bounds read in the 7-Zip NTFS handler allows attackers to disclose memory contents via crafted archives, impacting server-side extraction services.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** Yes
- **Published:** 3 Jul 2024
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2023-52169, GHSA-g8p4-4qgr-rf4f, UBUNTU-CVE-2023-52169

## What is CVE-2023-52169?

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

### Official description

The NtfsHandler.cpp NTFS handler in 7-Zip before 24.01 (for 7zz) contains an out-of-bounds read that allows an attacker to read beyond the intended buffer. The bytes read beyond the intended buffer are presented as a part of a filename listed in the file system image. This has security relevance in some known web-service use cases where untrusted users can upload files and have them extracted by a server-side 7-Zip process.

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

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


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

Upgrade to a fixed version.

## Is CVE-2023-52169 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-52169 is a high-severity vulnerability in n/a, published on 3 Jul 2024. 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-52169 in the wild and no public exploit code.

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

## Sources

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

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