LiveActive security incident?Get immediate response
CVE Record

CVE-2017-12652: libpng before 1.6.32 does not properly check the length of chunks against the user limit.

libpng before 1.6.32 does not properly check the length of chunks against the user limit.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2017-12652 is a critical input-validation flaw in libpng before 1.6.32. Software that processes PNG files using an affected libpng build may fail to enforce chunk length limits. Business risk is highest where untrusted images are accepted or processed automatically.

Executive priority

Prioritize remediation for externally reachable image-processing workflows and vendor products that bundle libpng. This is critical severity, but urgency should be driven by confirmed use of affected libpng and exposure to untrusted PNG files.

Technical view

libpng before 1.6.32 did not properly check PNG chunk lengths against the configured user limit. The CVE is mapped to CWE-20 and carries CVSS 3.1 score 9.8. The source bundle does not identify precise downstream affected versions beyond libpng and vendor advisories.

Likely exposure

Exposure is likely in applications, appliances, or embedded products that include libpng before 1.6.32 and process PNGs from users, partners, email, web uploads, or automated feeds. The affected CPE data is incomplete, so inventory verification is required.

Exploitation context

The provided sources do not show CISA KEV listing or other evidence of active exploitation. The CVSS vector indicates network-reachable, low-complexity, unauthenticated impact, but researchers should avoid assuming exploit availability without vendor or threat-intelligence confirmation.

Researcher notes

The CVE record gives a concise flaw description and high CVSS score, but downstream affected product data is sparse. Treat source evidence as sufficient for libpng version triage, not for naming unsupported affected products or claiming active exploitation.

Mitigation direction

  • Upgrade libpng to version 1.6.32 or later where directly managed.
  • Check vendor guidance for products that bundle libpng, including listed F5 and NetApp advisories.
  • Prioritize systems that process PNG files from untrusted or external sources.
  • Rebuild or redeploy statically linked applications after updating libpng.
  • Temporarily restrict untrusted PNG processing where updates cannot be confirmed.

Validation and detection

  • Inventory package managers, containers, firmware, and SBOMs for libpng versions before 1.6.32.
  • Check statically linked binaries and bundled third-party libraries for embedded libpng copies.
  • Confirm vendor appliance status against the relevant F5 or NetApp advisory.
  • Verify deployed builds use the remediated libpng version after patching.
  • Review image upload and processing paths for untrusted PNG exposure.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-12652 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2017-12652Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.