Skip to content
Fencer Vulns
medium 4.3

CVE-2009-1885 json

Stack consumption vulnerability in validators/DTD/DTDScanner.cpp in Apache Xerces C++ 2.7.0 and 2.8.0 allows context-dependent attackers to…

published 2009-08-11 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-1880

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

Summary

Stack consumption vulnerability in validators/DTD/DTDScanner.cpp in Apache Xerces C++ 2.7.0 and 2.8.0 allows context-dependent attackers to cause a denial of service (application crash) via vectors involving nested parentheses and invalid byte values in "simply nested DTD structures," as demonstrated by the Codenomicon XML fuzzing framework.

Patch / fix

  • xerces-c Debian 14, Debian 13, Debian 12 3.0.1-2

debian advisories DEBIAN-CVE-2009-1885

  • xerces-c openSUSE Tumbleweed 3.1.4-1.3

opensuse advisories openSUSE-SU-2024:10039-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-2009-1885 updated cvss 4.3

xerces-c27: Stack overflow when parsing recursive XML structures

  • Red Hat Enterprise MRG 1 xerces-c Red Hat Enterprise MRG 2 xerces-c
    affected: no fix planned “Will not fix”

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

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

Exploits and checks

  • svn.apache.org http://svn.apache.org/viewvc?view=rev&revision=781488 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

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.