CVE-2018-15470: An issue was discovered in Xen through 4.11.x.
Noroxi assessment
Priority: Monitor (action score 26/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: 0.39% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: xen (Alpine:v3.10) 4.11.1-r0; xen (Alpine:v3.6) 4.8.5-r0; xen (Alpine:v3.7) 4.9.3-r0.
Low priority for now. Upgrade to xen (Alpine:v3.10) 4.11.1-r0; xen (Alpine:v3.6) 4.8.5-r0; xen (Alpine:v3.7) 4.9.3-r0 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
An issue was discovered in Xen through 4.11.x. The logic in oxenstored for handling writes depended on the order of evaluation of expressions making up a tuple. As indicated in section 7.7.3 "Operations on data structures" of the OCaml manual, the order of evaluation of subexpressions is not specified. In practice, different implementations behave differently. Thus, oxenstored may not enforce the configured quota-maxentity. This allows a malicious or buggy guest to write as many xenstore entries as it wishes, causing unbounded memory usage in oxenstored. This can lead to a system-wide DoS.
- Published
- Aug 17, 2018
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 34th percentile
- CWE
- CWE-400
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.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 |
|---|---|---|
| xen | xen | cpe:2.3:o:xen:xen |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- xen xenup to 4.11.0 inclusive
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 | xen | before 4.11.1-r0 | 4.11.1-r0 |
| Alpine:v3.6 | xen | before 4.8.5-r0 | 4.8.5-r0 |
| Alpine:v3.7 | xen | before 4.9.3-r0 | 4.9.3-r0 |
| Alpine:v3.8 | xen | before 4.10.1-r3 | 4.10.1-r3 |
| Debian:12 | xen | before 4.11.1~pre.20180911.5acdd26fdc+dfsg-2 | 4.11.1~pre.20180911.5acdd26fdc+dfsg-2 |
| Debian:8 | xen | before 4.4.4lts4-0+deb8u1 | 4.4.4lts4-0+deb8u1 |
| Debian:9 | xen | before 4.8.4+xsa273+shim4.10.1+xsa273-1+deb9u10 | 4.8.4+xsa273+shim4.10.1+xsa273-1+deb9u10 |
| SUSE:Linux Enterprise Desktop 12 SP3 | xen | before 4.9.3_03-3.44.2 | 4.9.3_03-3.44.2 |
| SUSE:Linux Enterprise Module for Basesystem 15 | xen | before 4.10.2_04-3.9.1 | 4.10.2_04-3.9.1 |
Same product
xen: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-10921The grant-table feature in Xen through 4.8.x does not ensure sufficient type counts for a GNTMAP_device_map and GNTMAP_host_map mapping…41Plan
- CVE-2017-10920The grant-table feature in Xen through 4.8.x mishandles a GNTMAP_device_map and GNTMAP_host_map mapping, when followed by only a…41Plan
- CVE-2017-10918Xen through 4.8.x does not validate memory allocations during certain P2M operations, which allows guest OS users to obtain privileged host…41Plan
Published before and after this one in the same product
- ← EarlierCVE-2018-15468Aug 17, 2018 · An issue was discovered in Xen through 4.11.x.24Monitor
- ← EarlierCVE-2018-15469Aug 17, 2018 · An issue was discovered in Xen through 4.11.x.26Monitor
- Later →CVE-2018-15471Aug 17, 2018 · An issue was discovered in xenvif_set_hash_mapping in drivers/net/xen-netback/hash.c in the Linux kernel through 4.18.1, as used in Xen…31Monitor
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:xen | 4.11.1-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:xen | 4.11.1~pre.20180911.5acdd26fdc+dfsg-2 · Debian:12 | Package registry (OSV) |
| suse:xen | 4.9.3_03-3.44.2 · SUSE:Linux Enterprise Desktop 12 SP3 | 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.
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
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.