CVE-2024-45492: An issue was discovered in libexpat before 2.6.3.
An issue was discovered in libexpat before 2.6.3. nextScaffoldPart in xmlparse.c can have an integer overflow for m_groupSize on 32-bit platforms (where UINT_MAX equals SIZE_MAX).
Security readout for executives and security teams
Plain-English summary
libexpat, a widely used XML parser, had an integer overflow before version 2.6.3 on 32-bit platforms. A crafted XML input could cause incorrect parser behavior with limited confidentiality, integrity, and availability impact. Business exposure depends on where vulnerable libexpat is embedded, including operating system packages, applications, and vendor products.
Executive priority
Treat as high priority where 32-bit systems or appliances parse XML from untrusted sources. For modern 64-bit-only environments, urgency is lower but still requires inventory confirmation because libexpat is commonly bundled inside products.
Technical view
The flaw is in nextScaffoldPart in xmlparse.c, where m_groupSize can overflow on 32-bit platforms where UINT_MAX equals SIZE_MAX. It is tracked as CWE-190 with CVSS 3.1 score 7.3: AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L. The relevant exposure is remote XML parsing using vulnerable libexpat before 2.6.3.
Likely exposure
Highest concern is systems using 32-bit builds of libexpat before 2.6.3 in network-reachable XML parsing paths. The source bundle does not provide a complete affected product list; downstream advisories from Debian, NetApp, and Siemens indicate embedded or packaged exposure should be verified.
Exploitation context
The CVE is not listed as CISA KEV in the supplied bundle, and no cited source here confirms active exploitation. The CVSS vector indicates remote, low-complexity, unauthenticated attack potential without user interaction, but the issue is platform-specific to 32-bit conditions.
Researcher notes
Evidence supports an integer overflow in libexpat before 2.6.3, specifically tied to 32-bit SIZE_MAX behavior. The supplied affected-product field is not populated, so downstream impact must be established through SBOMs, package metadata, and vendor advisories rather than assumptions.
Mitigation direction
Upgrade libexpat to 2.6.3 or later where directly managed.
Apply vendor-provided fixed packages for bundled libexpat dependencies.
Review Debian, NetApp, and Siemens advisories for affected deployments.
Prioritize internet-facing XML parsing services on 32-bit platforms.
If fixes are unavailable, consult vendor guidance for supported compensating controls.
Validation and detection
Inventory libexpat versions across servers, containers, firmware, and appliances.
Identify 32-bit platforms or 32-bit userland builds using libexpat.
Map applications that parse untrusted XML over network interfaces.
Check vendor advisories for product-specific affected and fixed versions.
Confirm package updates or rebuilt dependencies include libexpat 2.6.3 or later.
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-190: 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.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-190 · source CWE mapping
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.