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

> Remote attackers can trigger a buffer overflow in libpng via crafted PNG images, potentially leading to arbitrary code execution or denial of service.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 17 Jul 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-45qx-49q8-7q26

## What is CVE-2011-2690?

CVE-2011-2690 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 17 Jul 2011. 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 libpng 1.0.x before 1.0.55, 1.2.x before 1.2.45, 1.4.x before 1.4.8, and 1.5.x before 1.5.4, when used by an application that calls the png_rgb_to_gray function but not the png_set_expand function, allows remote attackers to overwrite memory with an arbitrary amount of data, and possibly have unspecified other impact, via a crafted PNG image.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 4 products.


Products: Canonical Ubuntu Linux, Debian Debian Linux, Fedoraproject Fedora, Libpng Libpng.

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

Upgrade to a fixed version.

## Is CVE-2011-2690 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-2690 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 17 Jul 2011. 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-2690 in the wild and no public exploit code.

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

## Sources

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

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