CVE-2018-9251: The xz_decomp function in xzlib.c in libxml2 2.9.8, if --with-lzma is used, allows remote attackers to cause a denial of service (infinite…
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.3% (FIRST EPSS); higher than 84.1% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
- Fixed version: libxml2 (Alpine:v3.10) 2.9.8-r1; libxml2 (openSUSE:Tumbleweed) 2.9.12-1.2; libxml2-debuginfo (Red Hat:enterprise_linux:8::appstream) 0:2.9.7-7.el8.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to libxml2 (Alpine:v3.10) 2.9.8-r1; libxml2 (openSUSE:Tumbleweed) 2.9.12-1.2; libxml2-debuginfo (Red Hat:enterprise_linux:8::appstream) 0:2.9.7-7.el8 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
The xz_decomp function in xzlib.c in libxml2 2.9.8, if --with-lzma is used, allows remote attackers to cause a denial of service (infinite loop) via a crafted XML file that triggers LZMA_MEMLIMIT_ERROR, as demonstrated by xmllint, a different vulnerability than CVE-2015-8035.
- Published
- Apr 3, 2018
- Updated
- Jun 16, 2026
- EPSS
- 2.3% · 84th percentile
- CWE
- CWE-835
Report tools
Action score
22
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- 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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux8.0
- xmlsoft libxml22.9.8
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | libxml2 | before 2.9.8-r1 | 2.9.8-r1 |
| openSUSE:Tumbleweed | libxml2 | before 2.9.12-1.2 | 2.9.12-1.2 |
| Red Hat:enterprise_linux:8::appstream | libxml2-debuginfo | before 0:2.9.7-7.el8 | 0:2.9.7-7.el8 |
| Red Hat:enterprise_linux:8::appstream | libxml2-debugsource | before 0:2.9.7-7.el8 | 0:2.9.7-7.el8 |
| Red Hat:enterprise_linux:8::appstream | libxml2-devel | before 0:2.9.7-7.el8 | 0:2.9.7-7.el8 |
| Red Hat:enterprise_linux:8::appstream | python3-libxml2-debuginfo | before 0:2.9.7-7.el8 | 0:2.9.7-7.el8 |
| Red Hat:enterprise_linux:8::baseos | libxml2 | before 0:2.9.7-7.el8 | 0:2.9.7-7.el8 |
| Red Hat:enterprise_linux:8::baseos | python3-libxml2 | before 0:2.9.7-7.el8 | 0:2.9.7-7.el8 |
| SUSE:Linux Enterprise Desktop 12 SP3 | libxml2 | before 2.9.4-46.15.1 | 2.9.4-46.15.1 |
| SUSE:Linux Enterprise Desktop 12 SP3 | python-libxml2 | before 2.9.4-46.15.1 | 2.9.4-46.15.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 | libxml2 | before 2.9.7-3.3.1 | 2.9.7-3.3.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 | python-libxml2-python | before 2.9.7-3.3.1 | 2.9.7-3.3.1 |
Same product
xmlsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2008-3529Heap-based buffer overflow in the xmlParseAttValueComplex function in parser.c in libxml2 before 2.7.0 allows context-dependent attackers…47Plan
- 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
Published before and after this one in the same product
- ← EarlierCVE-2017-16932Nov 23, 2017 · parser.c in libxml2 before 2.9.5 does not prevent infinite recursion in parameter entities.32Monitor
- ← EarlierCVE-2017-7375Feb 19, 2018 · A flaw in libxml2 allows remote XML entity inclusion with default parser flags (i.e., when the caller did not request entity substitution…40Plan
- Later →CVE-2017-18258Apr 8, 2018 · The xz_head function in xzlib.c in libxml2 before 2.9.6 allows remote attackers to cause a denial of service (memory consumption) via a…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 |
|---|---|---|
| alpine:libxml2 | 2.9.8-r1 · Alpine:v3.10 | Package registry (OSV) |
| opensuse:libxml2 | 2.9.12-1.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:libxml2 | 0:2.9.7-7.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:libxml2-debuginfo | 0:2.9.7-7.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:libxml2-debugsource | 0:2.9.7-7.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:libxml2-devel | 0:2.9.7-7.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:python3-libxml2 | 0:2.9.7-7.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:python3-libxml2-debuginfo | 0:2.9.7-7.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| suse:libxml2 | 2.9.7-3.3.1 · SUSE:Linux Enterprise Module for Basesystem 15 | Package registry (OSV) |
| suse:python-libxml2 | 2.9.4-46.15.1 · SUSE:Linux Enterprise Desktop 12 SP3 | Package registry (OSV) |
| suse:python-libxml2-python | 2.9.7-3.3.1 · SUSE:Linux Enterprise Module for Basesystem 15 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-905 · Oct 30, 2020(OpenShift Güvenlik Güncellemesi)
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
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')CVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H
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
Vendor advisories and official records. Exploit/PoC links are deliberately left out.