# CVE-2011-3464: Memory corruption in n/a

> Remote attackers can cause application crashes or execute arbitrary code via a stack-based buffer overflow in libpng, requiring user interaction to process a malicious image.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/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:** No
- **Published:** 22 Jul 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-g3wr-53jg-9w4j

## What is CVE-2011-3464?

CVE-2011-3464 is a high-severity memory corruption vulnerability in Libpng Libpng, published on 22 Jul 2012. 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

Off-by-one error in the png_formatted_warning function in pngerror.c in libpng 1.5.4 through 1.5.7 might allow remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via unspecified vectors, which trigger a stack-based buffer overflow.

Weakness: CWE-189

## Which versions are affected by CVE-2011-3464?

It affects 1 product.


Products: Libpng Libpng.

## How do I fix CVE-2011-3464?

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

## Is CVE-2011-3464 being exploited?

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

## Other vulnerabilities in Libpng Libpng

- [CVE-2017-12652](https://insights.sbomify.com/CVE-2017-12652/): Denial of service in n/a (critical 9.8)
- [CVE-2018-14550](https://insights.sbomify.com/CVE-2018-14550/): Out-of-bounds write in libpng (high 8.8)
- [CVE-2026-25646](https://insights.sbomify.com/CVE-2026-25646/): LIBPNG has a heap buffer overflow in png_set_quantize (high 8.3)
- [CVE-2026-33636](https://insights.sbomify.com/CVE-2026-33636/): LIBPNG has ARM NEON Palette Expansion Out-of-Bounds Read on AArch64 (high 7.6)
- [CVE-2026-33416](https://insights.sbomify.com/CVE-2026-33416/): LIBPNG has use-after-free via pointer aliasing in `png_set_tRNS` and `png_set_PLTE` (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-3464 and fix it if it is affected.

What it is: CVE-2011-3464 is a high-severity memory corruption vulnerability in Libpng Libpng, published on 22 Jul 2012. 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-2011-3464 in the wild and no public exploit code.

Affected product: Libpng Libpng. 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-2011-3464/ (Markdown: https://insights.sbomify.com/CVE-2011-3464/index.md)
```

## Sources

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

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