# CVE-2024-39133: Memory corruption in n/a

> Attackers can cause a denial of service via heap buffer overflow in the zziplib library's zip parsing function.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** AZL-43591, AZL-44520, DEBIAN-CVE-2024-39133, GHSA-pmxx-f7h9-2q7w, UBUNTU-CVE-2024-39133

## What is CVE-2024-39133?

CVE-2024-39133 is a medium-severity memory corruption vulnerability in n/a, published on 27 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Heap Buffer Overflow vulnerability in zziplib v0.13.77 allows attackers to cause a denial of service via the __zzip_parse_root_directory() function at /zzip/zip.c.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2024-39133?

It affects 1 product.


Products: Zziplib Project Zziplib.

## How do I fix CVE-2024-39133?

Upgrade to a fixed version.

## Is CVE-2024-39133 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-39133 and fix it if it is affected.

What it is: CVE-2024-39133 is a medium-severity memory corruption vulnerability in n/a, published on 27 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39133 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-2024-39133/ (Markdown: https://insights.sbomify.com/CVE-2024-39133/index.md)
```

## Sources

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

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