Multiple use-after-free vulnerabilities in libxml2 2.5.10, 2.6.16, 2.6.26, 2.6.27, and 2.6.32, and libxml 1.8.17, allow context-dependent at

Affected versions

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

• apple iphone os2.0 and later · before 4.0
• apple mac os x10.5.0 and later · before 10.5.8
• apple mac os x10.6.0 and later · before 10.6.2
• apple mac os xbefore 10.4.11
• apple mac os x serverbefore 10.4.11
• apple mac os x server10.6.0 and later · before 10.6.2
• apple mac os x server10.5.0 and later · before 10.5.8
• apple safaribefore 4.0.4
• canonical ubuntu linux6.06
• canonical ubuntu linux8.04
• canonical ubuntu linux8.10
• canonical ubuntu linux9.04
• debian debian linux4.0
• fedoraproject fedora10
• fedoraproject fedora11
• google chromebefore 2.0.172.43
• opensuse opensuse10.3 and later · up to 11.1 inclusive
• redhat enterprise linux3.0
• redhat enterprise linux4.0
• redhat enterprise linux5.0

Package-level exposure

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

Other highest-scoring records for the same primary product.

• CVE-2004-0989Multiple buffer overflows in libXML 2.6.12 and 2.6.13 (libxml2), and possibly other versions, may allow remote attackers to execute arbitrar
  47Plan
• CVE-2008-4226Integer overflow in the xmlSAX2Characters function in libxml2 2.7.2 allows context-dependent attackers to cause a denial of service (memory
  41Plan
• CVE-2004-0110Buffer overflow in the (1) nanohttp or (2) nanoftp modules in XMLSoft Libxml 2 (Libxml2) 2.6.0 through 2.6.5 allow remote attackers to execu
  37Monitor
• CVE-2008-4225Integer overflow in the xmlBufferResize function in libxml2 2.7.2 allows context-dependent attackers to cause a denial of service (infinite
  32Monitor
• CVE-2009-2414Stack consumption vulnerability in libxml2 2.5.10, 2.6.16, 2.6.26, 2.6.27, and 2.6.32, and libxml 1.8.17, allows context-dependent attackers
  18Monitor

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

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1free(dev->buf);2/* ... another thread is still running ... */3process(dev->buf);

1lock(&dev->lock);2free(dev->buf);3dev->buf = NULL;4unlock(&dev->lock);

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.