# CVE-2023-39136: Denial of service in n/a

> Attackers can cause a Denial of Service in applications using ZipArchive by providing a crafted zip file that triggers an unhandled edge case.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Aug 2023
- **Updated:** 1 Oct 2024
- **Also known as:** GHSA-rh4c-32wr-89cj

## What is CVE-2023-39136?

CVE-2023-39136 is a medium-severity denial of service vulnerability in n/a, published on 30 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

An unhandled edge case in the component _sanitizedPath of ZipArchive v2.5.4 allows attackers to cause a Denial of Service (DoS) via a crafted zip file.

Weakness: CWE-703 (Improper Check or Handling of Exceptional Conditions)

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

It affects 1 product.


Products: Ziparchive Project Ziparchive.

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

No fix has been published for CVE-2023-39136 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-39136 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-36943](https://insights.sbomify.com/CVE-2022-36943/): Path traversal in SSZipArchive (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-39136 is a medium-severity denial of service vulnerability in n/a, published on 30 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-2023-39136 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-39136/ (Markdown: https://insights.sbomify.com/CVE-2023-39136/index.md)
```

## Sources

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

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