Skip to main content
VulnerabilityPublished Updated

CVE-2011-3045: libpng · Signed to Unsigned Conversion Error

Source CVE Database V5

0

Mentioned vulnerabilities

Not known to be exploited · CVSS 8.8 High : upgrade to 1.4.10beta01 soon.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
3.5% chance of exploitation in 30 days – higher than 89% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.4.10beta01
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Mar 2012

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade the Debian debian/libpng package to 1.4.10beta01.

Affected software

ProductAffectedFixed in
Debiandebian/libpngpkg:deb/debian/libpngOther threatsAffected
  • <1.4.10beta01
Fixed in
  • 1.4.10beta01

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2011-3045 effectively, European organizations should: 1) Ensure all software components using libpng are updated to version 1.4.10beta01 or later, or apply vendor-provided patches that address this vulnerability. 2) Upgrade Google Chrome browsers to versions 17.0.963.83 or later, or preferably to the latest stable release to benefit from all security fixes. 3) Implement strict email and web content filtering to detect and block malicious PNG files, reducing the risk of user exposure to crafted images. 4) Educate users about the risks of opening unsolicited or suspicious image files, especially from untrusted sources, to reduce successful exploitation via social engineering. 5) Employ endpoint protection solutions capable of detecting anomalous behavior or exploitation attempts related to image processing. 6) Conduct regular vulnerability assessments and software inventory audits to identify and remediate outdated libpng versions or vulnerable applications. 7) For organizations with legacy systems that cannot be immediately updated, consider isolating or restricting those systems' network access to limit exposure. These targeted actions go beyond generic patching advice by focusing on user awareness, filtering controls, and legacy system management.

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.

References

Community reviews

Loading reviews…