# CVE-2002-0728: Memory corruption in n/a

> Attackers can cause a denial of service via a crafted PNG file exploiting a buffer overflow in libpng's progressive reader.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Jul 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-hm75-38g4-x8xm

## What is CVE-2002-0728?

CVE-2002-0728 is a medium-severity memory corruption vulnerability in n/a, published on 26 Jul 2002. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in the progressive reader for libpng 1.2.x before 1.2.4, and 1.0.x before 1.0.14, allows attackers to cause a denial of service (crash) via a PNG data stream that has more IDAT data than indicated by the IHDR chunk.

## Which versions are affected by CVE-2002-0728?

It affects 1 product.


Products: Greg Roelofs Libpng.

## How do I fix CVE-2002-0728?

Upgrade to a fixed version.

## Is CVE-2002-0728 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0597](https://insights.sbomify.com/CVE-2004-0597/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-3334](https://insights.sbomify.com/CVE-2006-3334/): Memory corruption in n/a (high 7.5)
- [CVE-2002-1363](https://insights.sbomify.com/CVE-2002-1363/): Memory corruption in n/a (high 7.5)
- [CVE-2002-0660](https://insights.sbomify.com/CVE-2002-0660/): Memory corruption in n/a (high 7.5)
- [CVE-2006-0481](https://insights.sbomify.com/CVE-2006-0481/): Memory corruption in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0728 and fix it if it is affected.

What it is: CVE-2002-0728 is a medium-severity memory corruption vulnerability in n/a, published on 26 Jul 2002. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2002-0728 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-2002-0728/ (Markdown: https://insights.sbomify.com/CVE-2002-0728/index.md)
```

## Sources

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

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