CVE-2018-15470
This allows a malicious or buggy guest to write as many xenstore entries as it wishes, causing unbounded memory usage in oxenstored.
Does this matter?
Lower severity and a low EPSS score (0.40%). Track it; it rarely justifies an emergency change on its own.
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 3.0
- 6.5 MEDIUMCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
- EPSS
- 0.40% probability · 34th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-400
- Affected
- xen/xen
- Source
- cve@mitre.org
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
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.