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.
References
Link | Resource |
---|---|
http://xenbits.xen.org/xsa/advisory-272.html | Vendor Advisory |
https://security.gentoo.org/glsa/201810-06 | Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2018/11/msg00013.html |
Configurations
Information
Published : 2018-08-17 11:29
Updated : 2018-11-13 03:29
NVD link : CVE-2018-15470
Mitre link : CVE-2018-15470
JSON object : View
CWE
CWE-400
Uncontrolled Resource Consumption
Products Affected
xen
- xen