# CVE-2022-47069: Memory corruption in n/a

> An out-of-bounds read in p7zip can cause a denial of service when processing malicious ZIP archives.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Aug 2023
- **Updated:** 20 Nov 2025
- **Also known as:** AZL-35094, DEBIAN-CVE-2022-47069, GHSA-hjgv-c5xv-9h9v, UBUNTU-CVE-2022-47069

## What is CVE-2022-47069?

CVE-2022-47069 is a high-severity memory corruption vulnerability in n/a, published on 22 Aug 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

p7zip 16.02 was discovered to contain a heap-buffer-overflow vulnerability via the function NArchive::NZip::CInArchive::FindCd(bool) at CPP/7zip/Archive/Zip/ZipIn.cpp. NOTE: the Supplier has found that this is not a buffer overflow; at most an out-of-bounds read can occur.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2022-47069?

It affects 1 product.


Products: 7-Zip P7zip.

## How do I fix CVE-2022-47069?

Apply the vendor's patch.

## Is CVE-2022-47069 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-111497](https://insights.sbomify.com/CVE-2026-111497/): Google Brotli Unchecked Return Value (critical 9.2, exploited in the wild)
- [CVE-2016-9296](https://insights.sbomify.com/CVE-2016-9296/): Null dereference in n/a (high 7.5)
- [CVE-2015-1038](https://insights.sbomify.com/CVE-2015-1038/): Path traversal in n/a (medium 5.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-47069 and fix it if it is affected.

What it is: CVE-2022-47069 is a high-severity memory corruption vulnerability in n/a, published on 22 Aug 2023. It can only be exploited from the same machine or local network, 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-2022-47069 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-2022-47069/ (Markdown: https://insights.sbomify.com/CVE-2022-47069/index.md)
```

## Sources

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

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