Vulnerability Description
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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Xen | Xen | <= 4.11.0 |
Related Weaknesses (CWE)
References
- http://xenbits.xen.org/xsa/advisory-272.htmlVendor Advisory
- https://lists.debian.org/debian-lts-announce/2018/11/msg00013.html
- https://security.gentoo.org/glsa/201810-06Third Party Advisory
- http://xenbits.xen.org/xsa/advisory-272.htmlVendor Advisory
- https://lists.debian.org/debian-lts-announce/2018/11/msg00013.html
- https://security.gentoo.org/glsa/201810-06Third Party Advisory
FAQ
What is CVE-2018-15470?
CVE-2018-15470 is a vulnerability with a CVSS score of 6.5 (MEDIUM). 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 "Operatio...
How severe is CVE-2018-15470?
CVE-2018-15470 has been rated MEDIUM with a CVSS base score of 6.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2018-15470?
Check the references section above for vendor advisories and patch information. Affected products include: Xen Xen.