# CVE-2004-0797: Denial of service in n/a

> Local attackers can crash applications using the ZLib library by exploiting error handling flaws in inflate functions.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-0797, GHSA-r2r9-xr4w-r49c

## What is CVE-2004-0797?

CVE-2004-0797 is a low-severity denial of service vulnerability in n/a, published on 14 Sep 2004. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The error handling in the (1) inflate and (2) inflateBack functions in ZLib compression library 1.2.x allows local users to cause a denial of service (application crash).

## Which versions are affected by CVE-2004-0797?

It affects 1 product.


Products: Zlib Zlib.

## How do I fix CVE-2004-0797?

Upgrade to a fixed version.

## Is CVE-2004-0797 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-0059](https://insights.sbomify.com/CVE-2002-0059/): Use after free in n/a (critical 9.8)
- [CVE-2005-2096](https://insights.sbomify.com/CVE-2005-2096/): Memory corruption in n/a (high 7.5)
- [CVE-2003-0107](https://insights.sbomify.com/CVE-2003-0107/): Memory corruption in n/a (high 7.5)
- [CVE-2005-1849](https://insights.sbomify.com/CVE-2005-1849/): Denial of service in n/a (medium 5.0)
- [CVE-2026-22184](https://insights.sbomify.com/CVE-2026-22184/): zlib <= 1.3.1.2 untgz Global Buffer Overflow in TGZfname() (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0797 and fix it if it is affected.

What it is: CVE-2004-0797 is a low-severity denial of service vulnerability in n/a, published on 14 Sep 2004. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-0797 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-2004-0797/ (Markdown: https://insights.sbomify.com/CVE-2004-0797/index.md)
```

## Sources

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

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