# CVE-2017-17969: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service via a crafted ZIP archive due to a heap-based buffer overflow in the 7-Zip library.

- **Severity:** High 7.8 (`CVSS:3.0/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:** 30 Jan 2018
- **Updated:** 10 Jan 2025
- **Also known as:** ALPINE-CVE-2017-17969, AZL-35092, AZL-6783, DEBIAN-CVE-2017-17969, DLA-1268-1, DSA-4104-1, GHSA-5mfm-p22h-8c37, MGASA-2018-0123, UBUNTU-CVE-2017-17969

## What is CVE-2017-17969?

CVE-2017-17969 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 30 Jan 2018. 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

Heap-based buffer overflow in the NCompress::NShrink::CDecoder::CodeReal method in 7-Zip before 18.00 and p7zip allows remote attackers to cause a denial of service (out-of-bounds write) or potentially execute arbitrary code via a crafted ZIP archive.

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

## Which versions are affected by CVE-2017-17969?

It affects 3 products.


Products: 7-Zip 7-Zip, 7-Zip P7zip, Debian Debian Linux.

## How do I fix CVE-2017-17969?

Upgrade to a fixed version.

## Is CVE-2017-17969 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2025-0411](https://insights.sbomify.com/CVE-2025-0411/): 7-Zip Mark of the Web Bypass (high 7.0, exploited in the wild)
- [CVE-2008-6536](https://insights.sbomify.com/CVE-2008-6536/): Other in n/a (critical 10.0)
- [CVE-2026-48095](https://insights.sbomify.com/CVE-2026-48095/): GHSL-2026-140_7-Zip: 7-Zip has a heap buffer overflow via NTFS compressed stream buffer under-allocation (high 8.8)
- [CVE-2018-10172](https://insights.sbomify.com/CVE-2018-10172/): Privilege escalation in n/a (high 8.8)
- [CVE-2016-2335](https://insights.sbomify.com/CVE-2016-2335/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-17969 and fix it if it is affected.

What it is: CVE-2017-17969 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 30 Jan 2018. 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: There is no known exploitation of CVE-2017-17969 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-2017-17969/ (Markdown: https://insights.sbomify.com/CVE-2017-17969/index.md)
```

## Sources

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

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