CVE-2018-15470
First published: Fri Aug 17 2018(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Xen xen-unstable | <=4.11.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2018-15470?
CVE-2018-15470 has been rated as a medium to high severity vulnerability.
How do I fix CVE-2018-15470?
To fix CVE-2018-15470, upgrade Xen to version 4.11.1 or later.
What systems are affected by CVE-2018-15470?
CVE-2018-15470 affects Xen versions up to and including 4.11.0.
What kind of vulnerability is CVE-2018-15470?
CVE-2018-15470 is a logic issue in the oxenstored component of Xen.
Is there a workaround for CVE-2018-15470?
There is no known workaround for CVE-2018-15470, so applying the patch is essential.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/references
- agent/weakness
- agent/last-modified-date
- agent/severity
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/xen
- canonical/xen xen-unstable
- version/xen xen-unstable/4.11.0