Skip to content
Fencer Intel
medium 4.3

CVE-2010-4008 json

libxml2 before 2.7.8, as used in Google Chrome before 7.0.517.44, Apple Safari 5.0.2 and earlier, and other products, reads from invalid me…

published 15y ago modified 4mo ago also EUVD-2010-3984

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.7%
EPSS 2.7% chance of exploitation in 30 days, percentile 86%
public exploits
0
none known

Summary

libxml2 before 2.7.8, as used in Google Chrome before 7.0.517.44, Apple Safari 5.0.2 and earlier, and other products, reads from invalid memory locations during processing of malformed XPath expressions, which allows context-dependent attackers to cause a denial of service (application crash) via a crafted XML document.

Patch / fix

  • google chrome 7.0.517.44
  • apple itunes 10.2
  • apple safari 5.0.4
  • xmlsoft libxml2 2.7.8
  • apache openoffice 3.3.0
  • apple iphone_os 4.2
  • apple mac_os_x 10.6.7
  • libxml2 Debian 14, Debian 13, Debian 12 2.7.8.dfsg-1

debian advisories DEBIAN-CVE-2010-4008

  • mingw32-libxml2 RHEL 6 2.7.6-6.el6_3
  • libxml2 RHEL 5 2.6.26-2.1.12.el5_7.2
  • libxml2-python RHEL 5 2.6.26-2.1.12.el5_7.2
  • libxml2 RHEL 6 2.7.6-4.el6
  • libxml2-python RHEL 6 2.7.6-4.el6

red hat advisories RHSA-2013:0217RHSA-2012:0017RHSA-2011:1749

Is CVE-2010-4008 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2010-4008 updated cvss 4.3

libxml2: Crash (stack frame overflow or NULL pointer dereference) by traversal of XPath axis

  • Red Hat Enterprise Linux (v. 5 server) libxml2 2.6.26-2.1.12.el5_7.2, libxml2-python 2.6.26-2.1.12.el5_7.2 Red Hat Enterprise Linux Desktop (v. 5 client) libxml2 2.6.26-2.1.12.el5_7.2, libxml2-python 2.6.26-2.1.12.el5_7.2
    fixed: vendor fix RHSA-2012:0017
  • Red Hat Enterprise Linux Desktop (v. 6) libxml2 2.7.6-4.el6, libxml2-python 2.7.6-4.el6
    fixed: vendor fix RHSA-2011:1749
  • Red Hat Enterprise Linux Desktop Optional (v. 6) libxml2 2.7.6-4.el6, mingw32-libxml2 2.7.6-6.el6_3
    fixed: vendor fix RHSA-2013:0217
  • Red Hat Enterprise Linux HPC Node (v. 6) libxml2 2.7.6-4.el6, libxml2-python 2.7.6-4.el6
    fixed: vendor fix RHSA-2011:1749
  • Red Hat Enterprise Linux HPC Node Optional (v. 6) libxml2 2.7.6-4.el6, mingw32-libxml2 2.7.6-6.el6_3
    fixed: vendor fix RHSA-2013:0217
  • Red Hat Enterprise Linux Server (v. 6) libxml2 2.7.6-4.el6, libxml2-python 2.7.6-4.el6
    fixed: vendor fix RHSA-2011:1749
  • Red Hat Enterprise Linux Server Optional (v. 6) libxml2 2.7.6-4.el6, mingw32-libxml2 2.7.6-6.el6_3
    fixed: vendor fix RHSA-2013:0217
  • Red Hat Enterprise Linux Workstation (v. 6) libxml2 2.7.6-4.el6, libxml2-python 2.7.6-4.el6
    fixed: vendor fix RHSA-2011:1749
show 3 more
  • Red Hat Enterprise Linux Workstation Optional (v. 6) libxml2 2.7.6-4.el6, mingw32-libxml2 2.7.6-6.el6_3
    fixed: vendor fix RHSA-2013:0217
  • Red Hat RHEL Desktop Workstation (v. 5 client) libxml2 2.6.26-2.1.12.el5_7.2
    fixed: vendor fix RHSA-2012:0017
  • Red Hat Enterprise Linux 4 libxml2
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.70% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • code.google.com http://code.google.com/p/chromium/issues/detail?id=58731 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.