CVE-2004-0989: Multiple buffer overflows in libXML 2.6.12 and 2.6.13 (libxml2), and possibly other versions, may allow remote attackers to execute…
Noroxi assessment
Priority: Plan (action score 47/100)
- Public proof-of-concept code exists (Exploit-DB); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 21.6% (FIRST EPSS); higher than 97.6% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: libxml2 (Debian:12) 2.6.11-5; libxml (Debian:3.0) 1.8.17-2woody2; libxml2 (Debian:3.0) 2.4.19-4woody2.
Add it to your regular patch cycle. Upgrade to libxml2 (Debian:12) 2.6.11-5; libxml (Debian:3.0) 1.8.17-2woody2; libxml2 (Debian:3.0) 2.4.19-4woody2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Multiple buffer overflows in libXML 2.6.12 and 2.6.13 (libxml2), and possibly other versions, may allow remote attackers to execute arbitrary code via (1) a long FTP URL that is not properly handled by the xmlNanoFTPScanURL function, (2) a long proxy URL containing FTP data that is not properly handled by the xmlNanoFTPScanProxy function, and other overflows related to manipulation of DNS length values, including (3) xmlNanoFTPConnect, (4) xmlNanoHTTPConnectHost, and (5) xmlNanoHTTPConnectHost.
- Published
- Mar 1, 2005
- Updated
- Jun 16, 2026
- EPSS
- 21.6% · 97th percentile
- CWE
- —
Report tools
Action score
47
Add it to your regular patch cycle.
- CVSS
- 40 / 40 · 10.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 7 / 30 · 21.6%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| xmlsoft | libxml | cpe:2.3:a:xmlsoft:libxml |
| xmlsoft | libxml2 | cpe:2.3:a:xmlsoft:libxml2 |
| xmlstarlet | command line xml toolkit | cpe:2.3:a:xmlstarlet:command_line_xml_toolkit |
| redhat | fedora core | cpe:2.3:o:redhat:fedora_core |
| trustix | secure linux | cpe:2.3:o:trustix:secure_linux |
| ubuntu | ubuntu linux | cpe:2.3:o:ubuntu:ubuntu_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat fedora corecore_2.0
- trustix secure linux2.0
- trustix secure linux2.1
- ubuntu ubuntu linux4.1
- xmlsoft libxml1.8.17
- xmlsoft libxml22.5.11
- xmlsoft libxml22.6.11
- xmlsoft libxml22.6.12
+7 more rows
- xmlsoft libxml22.6.13
- xmlsoft libxml22.6.14
- xmlsoft libxml22.6.6
- xmlsoft libxml22.6.7
- xmlsoft libxml22.6.8
- xmlsoft libxml22.6.9
- xmlstarlet command line xml toolkit0.9.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | libxml2 | before 2.6.11-5 | 2.6.11-5 |
| Debian:3.0 | libxml | before 1.8.17-2woody2 | 1.8.17-2woody2 |
| Debian:3.0 | libxml2 | before 2.4.19-4woody2 | 2.4.19-4woody2 |
| Red Hat:enterprise_linux:3::as | libxml | before 1:1.8.17-9.2 | 1:1.8.17-9.2 |
| Red Hat:enterprise_linux:3::as | libxml-debuginfo | before 1:1.8.17-9.2 | 1:1.8.17-9.2 |
| Red Hat:enterprise_linux:3::as | libxml-devel | before 1:1.8.17-9.2 | 1:1.8.17-9.2 |
| Red Hat:enterprise_linux:3::as | libxml2 | before 0:2.5.10-7 | 0:2.5.10-7 |
| Red Hat:enterprise_linux:3::as | libxml2-debuginfo | before 0:2.5.10-7 | 0:2.5.10-7 |
| Red Hat:enterprise_linux:3::as | libxml2-devel | before 0:2.5.10-7 | 0:2.5.10-7 |
| Red Hat:enterprise_linux:3::as | libxml2-python | before 0:2.5.10-7 | 0:2.5.10-7 |
Same product
xmlsoft: all recordsOther highest-scoring records for the same primary product.
- 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…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
Published before and after this one in the same product
- Later →CVE-2009-2414Aug 11, 2009 · Stack 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…18Monitor
- Later →CVE-2009-2416Aug 11, 2009 · 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…27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:libxml | 1.8.17-2woody2 · Debian:3.0 | Package registry (OSV) |
| debian:libxml2 | 2.6.11-5 · Debian:12 | Package registry (OSV) |
| red hat:libxml | 1:1.8.17-9.2 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:libxml-debuginfo | 1:1.8.17-9.2 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:libxml-devel | 1:1.8.17-9.2 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:libxml2 | 0:2.5.10-7 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:libxml2-debuginfo | 0:2.5.10-7 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:libxml2-devel | 0:2.5.10-7 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:libxml2-python | 0:2.5.10-7 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | remote | 2004-10-26 |
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.
- First PoC-126 d
- Published
- TodayNov 16, 2026+7930 d
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
—
CVSS vector
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- lists.apple.com/archives/security-announce/2005/Jan/msg00001.html
- marc.info/?l=bugtraq&m=109880813013482&w=2
- secunia.com/advisories/13000
- securitytracker.com/id?1011941
- www.ciac.org/ciac/bulletins/p-029.shtml
- www.debian.org/security/2004/dsa-582
- www.gentoo.org/security/en/glsa/glsa-200411-05.xml
- www.novell.com/linux/security/advisories/2005_01_sr.html
- www.osvdb.org/11179
- www.osvdb.org/11180
- www.osvdb.org/11324
- www.redhat.com/support/errata/RHSA-2004-615.html
- www.redhat.com/support/errata/RHSA-2004-650.html
- exchange.xforce.ibmcloud.com/vulnerabilities/17870
- exchange.xforce.ibmcloud.com/vulnerabilities/17872
- exchange.xforce.ibmcloud.com/vulnerabilities/17875
- exchange.xforce.ibmcloud.com/vulnerabilities/17876
- oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10505
- oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A1173
Vendor advisories and official records. Exploit/PoC links are deliberately left out.