# CVE-2011-3045: Integer overflow in n/a > Remote attackers can cause application crashes or execute arbitrary code via crafted PNG files due to an integer signedness error in libpng. - **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:** 22 Mar 2012 - **Updated:** 9 Jun 2025 - **Also known as:** AZL-41243, DSA-2439-1, GHSA-w4pv-vqp3-f753, RHSA-2012:0407 ## What is CVE-2011-3045? CVE-2011-3045 is a high-severity vulnerability in Debian Debian Linux, published on 22 Mar 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 Integer signedness error in the png_inflate function in pngrutil.c in libpng before 1.4.10beta01, as used in Google Chrome before 17.0.963.83 and other products, allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted PNG file, a different vulnerability than CVE-2011-3026. Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-195 (Signed to Unsigned Conversion Error) ## Which versions are affected by CVE-2011-3045? It affects 13 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libpng` | Red Hat:enterprise_linux:5::client | All versions | 2:1.2.10-16.el5_8 | | `libpng-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 2:1.2.10-16.el5_8 | | `libpng` | Red Hat:enterprise_linux:5::client_workstation | All versions | 2:1.2.10-16.el5_8 | | `libpng-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 2:1.2.10-16.el5_8 | | `libpng-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 2:1.2.10-16.el5_8 | | `libpng` | Red Hat:enterprise_linux:5::server | All versions | 2:1.2.10-16.el5_8 | | `libpng-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 2:1.2.10-16.el5_8 | | `libpng-devel` | Red Hat:enterprise_linux:5::server | All versions | 2:1.2.10-16.el5_8 | | `libpng` | Red Hat:enterprise_linux:6::client | All versions | 2:1.2.48-1.el6_2 | | `libpng-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 2:1.2.48-1.el6_2 | | `libpng-devel` | Red Hat:enterprise_linux:6::client | All versions | 2:1.2.48-1.el6_2 | | `libpng-static` | Red Hat:enterprise_linux:6::client | All versions | 2:1.2.48-1.el6_2 | | `libpng` | Red Hat:enterprise_linux:6::computenode | All versions | 2:1.2.48-1.el6_2 | | `libpng-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 2:1.2.48-1.el6_2 | | `libpng-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 2:1.2.48-1.el6_2 | | `libpng-static` | Red Hat:enterprise_linux:6::computenode | All versions | 2:1.2.48-1.el6_2 | | `libpng` | Red Hat:enterprise_linux:6::server | All versions | 2:1.2.48-1.el6_2 | | `libpng-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 2:1.2.48-1.el6_2 | | `libpng-devel` | Red Hat:enterprise_linux:6::server | All versions | 2:1.2.48-1.el6_2 | | `libpng-static` | Red Hat:enterprise_linux:6::server | All versions | 2:1.2.48-1.el6_2 | | `libpng` | Red Hat:enterprise_linux:6::workstation | All versions | 2:1.2.48-1.el6_2 | | `libpng-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 2:1.2.48-1.el6_2 | | `libpng-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 2:1.2.48-1.el6_2 | | `libpng-static` | Red Hat:enterprise_linux:6::workstation | All versions | 2:1.2.48-1.el6_2 | Products: Debian Debian Linux, Fedoraproject Fedora, Google Chrome, Libpng Libpng, Opensuse Opensuse, Redhat Enterprise Linux, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Eus, Redhat Enterprise Linux Workstation, Redhat Gluster Storage, Redhat Storage, Redhat Storage for Public Cloud. ## How do I fix CVE-2011-3045? Upgrade to a fixed version. ## Is CVE-2011-3045 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-3045 exists. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2011-3045 and fix it if it is affected. What it is: CVE-2011-3045 is a high-severity vulnerability in Debian Debian Linux, published on 22 Mar 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-3045 exists. Affected product: Debian Debian 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-3045/ (Markdown: https://insights.sbomify.com/CVE-2011-3045/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2011-3045 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-3045 - OSV: https://osv.dev/vulnerability/CVE-2011-3045 --- From sbomify Insights: https://insights.sbomify.com/CVE-2011-3045/ Summaries are generated and may contain mistakes; the official description above is the record.