Skip to content
Fencer Vulns
medium 5.0

CVE-2008-4409 json

libxml2 2.7.0 and 2.7.1 does not properly handle "predefined entities definitions" in entities, which allows context-dependent attackers to…

published 2008-10-03 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-4390

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
8.5%
EPSS 8.5% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB

Summary

libxml2 2.7.0 and 2.7.1 does not properly handle "predefined entities definitions" in entities, which allows context-dependent attackers to cause a denial of service (memory consumption and application crash), as demonstrated by use of xmllint on a certain XML document, a different vulnerability than CVE-2003-1564 and CVE-2008-3281.

Patch / fix

  • libxml2 openSUSE Tumbleweed 2.9.4-1.22
  • python-libxml2 openSUSE Tumbleweed 2.9.4-1.4

opensuse advisories openSUSE-SU-2024:10192-1openSUSE-SU-2024:10228-1

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-2008-4409 updated

libxml2: infinite loop when entity is used in entity definition

  • Red Hat All currently supported Red Hat products
    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

Timeline

  1. First public exploit (EDB-32454)
  2. Published

Exploit prediction

8.53% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-32454 libxml2 - Denial of Service dos, 2008-10-02
  • bugzilla.gnome.org http://bugzilla.gnome.org/show_bug.cgi?id=554660 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • CWE-399 Resource Management Errors

References

Sources

Fencer Vulns 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.