Skip to content
Noroxi
CVE-2012-1148· NVD / CVE Program· CNA redhat

Memory leak in the poolGrow function in expat/lib/xmlparse.c in expat before 2.1.0 allows context-dependent attackers to cause a denial of s

Memory leak in the poolGrow function in expat/lib/xmlparse.c in expat before 2.1.0 allows context-dependent attackers to cause a denial of service (memory consumption) via a large number of crafted XML files that cause improperly-handled reallocation failures when expanding entities.

MediumCVSS 5.0 · v2.0—No exploit Fix available
Published
Jul 3, 2012
Updated
Jun 16, 2026
EPSS
3.6% · 89th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
20 / 40 · 5.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.6%

Affected systems

VendorProduct
libexpat projectlibexpat
applemac os x

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apple mac os xup to 10.11.1 inclusive
  • libexpat project libexpatup to 2.0.1 inclusive
  • libexpat project libexpat1.95.1
  • libexpat project libexpat1.95.2
  • libexpat project libexpat1.95.4
  • libexpat project libexpat1.95.5
  • libexpat project libexpat1.95.6
  • libexpat project libexpat1.95.7
  • libexpat project libexpat1.95.8
  • libexpat project libexpat2.0.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12expatbefore 2.1.0~beta3-12.1.0~beta3-1
Debian:12libxmltokall versions—
Debian:12xmlrpc-cbefore 1.16.33-3.21.16.33-3.2
Debian:6.0expatbefore 2.0.1-7+squeeze12.0.1-7+squeeze1
openSUSE:Tumbleweedexpatbefore 2.2.0-3.12.2.0-3.1
Red Hat:enterprise_linux:5::clientexpatbefore 0:1.95.8-11.el5_80:1.95.8-11.el5_8
Red Hat:enterprise_linux:5::clientexpat-debuginfobefore 0:1.95.8-11.el5_80:1.95.8-11.el5_8
Red Hat:enterprise_linux:5::client_workstationexpat-develbefore 0:1.95.8-11.el5_80:1.95.8-11.el5_8
Red Hat:enterprise_linux:6::clientexpatbefore 0:2.0.1-11.el6_20:2.0.1-11.el6_2
Red Hat:enterprise_linux:6::clientexpat-debuginfobefore 0:2.0.1-11.el6_20:2.0.1-11.el6_2
Red Hat:enterprise_linux:6::clientexpat-develbefore 0:2.0.1-11.el6_20:2.0.1-11.el6_2

Other highest-scoring records for the same primary product.

  • CVE-2022-25236xmlparse.c in Expat (aka libexpat) before 2.4.5 allows attackers to insert namespace-separator characters into namespace URIs.
    50Plan
  • CVE-2022-25315In Expat (aka libexpat) before 2.4.5, there is an integer overflow in storeRawNames.
    40Plan
  • CVE-2022-25235xmltok_impl.c in Expat (aka libexpat) before 2.4.5 lacks certain validation of encoding, such as checks for whether a UTF-8 character is val
    40Plan
  • CVE-2022-23852Expat (aka libexpat) before 2.4.4 has a signed integer overflow in XML_GetBuffer, for configurations with a nonzero XML_CONTEXT_BYTES.
    40Plan
  • CVE-2022-22824defineAttribute in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.
    40Plan
  • CVE-2022-22823build_model in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:expat2.1.0~beta3-1 · Debian:12Package registry (OSV)
debian:xmlrpc-c1.16.33-3.2 · Debian:12Package registry (OSV)
opensuse:expat2.2.0-3.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:expat0:1.95.8-11.el5_8 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:expat-debuginfo0:1.95.8-11.el5_8 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:expat-devel0:1.95.8-11.el5_8 · Red Hat:enterprise_linux:5::client_workstationPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
P · the service can be disrupted
Attack complexity
Low
Confidentiality impact
None
Integrity impact
None
Availability impact
P

CVSS vector

AV:N/AC:L/Au:N/C:N/I:N/A:P

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records