CVE-2008-3529: Heap-based buffer overflow in the xmlParseAttValueComplex function in parser.c in libxml2 before 2.7.0 allows context-dependent attackers to…
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: 23.3% (FIRST EPSS); higher than 97.8% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: libxml2 (Debian:12) 2.6.32.dfsg-4; libxml2 (Debian:4.0) 2.6.27.dfsg-5; libxml2 (Red Hat:enterprise_linux:2.1::as) 0:2.4.19-11.ent.
Add it to your regular patch cycle. Upgrade to libxml2 (Debian:12) 2.6.32.dfsg-4; libxml2 (Debian:4.0) 2.6.27.dfsg-5; libxml2 (Red Hat:enterprise_linux:2.1::as) 0:2.4.19-11.ent 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
Heap-based buffer overflow in the xmlParseAttValueComplex function in parser.c in libxml2 before 2.7.0 allows context-dependent attackers to cause a denial of service (crash) or execute arbitrary code via a long XML entity name.
- Published
- Sep 12, 2008
- Updated
- Jun 16, 2026
- EPSS
- 23.3% · 97th percentile
- CWE
- CWE-119
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 · 23.3%
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 | libxml2 | cpe:2.3:a:xmlsoft:libxml2 |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| apple | safari | cpe:2.3:a:apple:safari |
| apple | iphone os | cpe:2.3:o:apple:iphone_os |
| apple | mac os x | cpe:2.3:o:apple:mac_os_x |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apple iphone osbefore 3.0
- apple mac os xbefore 10.5.7
- apple mac os x10.5.7
- apple safari3.2.0 and later · before 3.2.3
- apple safaribefore 4.0
- canonical ubuntu linux6.06
- canonical ubuntu linux7.04
- canonical ubuntu linux7.10
+5 more rows
- canonical ubuntu linux8.04
- canonical ubuntu linux8.10
- canonical ubuntu linux9.04
- debian debian linux4.0
- xmlsoft libxml2before 2.7.0
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.32.dfsg-4 | 2.6.32.dfsg-4 |
| Debian:4.0 | libxml2 | before 2.6.27.dfsg-5 | 2.6.27.dfsg-5 |
| Red Hat:enterprise_linux:2.1::as | libxml2 | before 0:2.4.19-11.ent | 0:2.4.19-11.ent |
| Red Hat:enterprise_linux:2.1::as | libxml2-devel | before 0:2.4.19-11.ent | 0:2.4.19-11.ent |
| Red Hat:enterprise_linux:2.1::as | libxml2-python | before 0:2.4.19-11.ent | 0:2.4.19-11.ent |
| Red Hat:enterprise_linux:3::as | libxml2 | before 0:2.5.10-13 | 0:2.5.10-13 |
| Red Hat:enterprise_linux:3::as | libxml2-debuginfo | before 0:2.5.10-13 | 0:2.5.10-13 |
| Red Hat:enterprise_linux:3::as | libxml2-devel | before 0:2.5.10-13 | 0:2.5.10-13 |
| Red Hat:enterprise_linux:3::as | libxml2-python | before 0:2.5.10-13 | 0:2.5.10-13 |
| Red Hat:enterprise_linux:4::as | libxml2 | before 0:2.6.16-12.5 | 0:2.6.16-12.5 |
| Red Hat:enterprise_linux:4::as | libxml2-debuginfo | before 0:2.6.16-12.5 | 0:2.6.16-12.5 |
| Red Hat:enterprise_linux:4::as | libxml2-devel | before 0:2.6.16-12.5 | 0:2.6.16-12.5 |
| Red Hat:enterprise_linux:4::as | libxml2-python | before 0:2.6.16-12.5 | 0:2.6.16-12.5 |
| Red Hat:enterprise_linux:5::client | libxml2-python | before 0:2.6.26-2.1.2.6 | 0:2.6.26-2.1.2.6 |
| Red Hat:enterprise_linux:5::client_workstation | libxml2 | before 0:2.6.26-2.1.2.6 | 0:2.6.26-2.1.2.6 |
| Red Hat:enterprise_linux:5::client_workstation | libxml2-debuginfo | before 0:2.6.26-2.1.2.6 | 0:2.6.26-2.1.2.6 |
| Red Hat:enterprise_linux:5::client_workstation | libxml2-devel | before 0:2.6.26-2.1.2.6 | 0:2.6.26-2.1.2.6 |
Same product
xmlsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-7376Buffer overflow in libxml2 allows remote attackers to execute arbitrary code by leveraging an incorrect limit for port values when handling…46Plan
- CVE-2022-40303An issue was discovered in libxml2 before 2.10.3.42Plan
- CVE-2021-3518There's a flaw in libxml2 in versions before 2.9.11.42Plan
Published before and after this one in the same product
- ← EarlierCVE-2003-1564Dec 31, 2003 · libxml2, possibly before 2.5.0, does not properly detect recursion during entity expansion, which allows context-dependent attackers to…26Monitor
- ← EarlierCVE-2008-3281Aug 27, 2008 · libxml2 2.6.32 and earlier does not properly detect recursion during entity expansion in an attribute value, which allows context-dependent…27Monitor
- Later →CVE-2008-4409Oct 3, 2008 · libxml2 2.7.0 and 2.7.1 does not properly handle "predefined entities definitions" in entities, which allows context-dependent attackers to…23Monitor
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:libxml2 | 2.6.32.dfsg-4 · Debian:12 | Package registry (OSV) |
| red hat:libxml2 | 0:2.5.10-13 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:libxml2-debuginfo | 0:2.5.10-13 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:libxml2-devel | 0:2.5.10-13 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:libxml2-python | 0:2.5.10-13 · 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 | dos | 2009-05-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.
- Published
- First PoC+255 d
- TodayNov 14, 2026+6637 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)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS 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.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
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/2009/Jun/msg00005.html
- lists.apple.com/archives/security-announce/2009/May/msg00000.html
- lists.apple.com/archives/security-announce/2009/jun/msg00002.html
- lists.opensuse.org/opensuse-security-announce/2008-09/msg00004.html
- secunia.com/advisories/31855
- secunia.com/advisories/31860
- secunia.com/advisories/31868
- secunia.com/advisories/31982
- secunia.com/advisories/32265
- secunia.com/advisories/32280
- secunia.com/advisories/32807
- secunia.com/advisories/32974
- secunia.com/advisories/33715
- secunia.com/advisories/33722
- secunia.com/advisories/35056
- secunia.com/advisories/35074
- secunia.com/advisories/35379
- secunia.com/advisories/36173
- secunia.com/advisories/36235
Vendor advisories and official records. Exploit/PoC links are deliberately left out.