CVE-2018-15470
published 2018-08-17CVE-2018-15470: 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…
PriorityP423medium6.5CVSS 3.0
AVLACLPRLUINSCCNINAH
EPSS
0.40%
32.3th percentile
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.
Affected
6 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | xen | < xen 4.11.1~pre.20180911.5acdd26fdc+dfsg-2 (bookworm) | xen 4.11.1~pre.20180911.5acdd26fdc+dfsg-2 (bookworm) |
| xen | xen | <= 4.11.0 | — |
| xen | xen | >= 0 < 4.11.1~pre.20180911.5acdd26fdc+dfsg-2 | 4.11.1~pre.20180911.5acdd26fdc+dfsg-2 |
| xen | xen | >= 0 < 4.11.1~pre.20180911.5acdd26fdc+dfsg-2 | 4.11.1~pre.20180911.5acdd26fdc+dfsg-2 |
| xen | xen | >= 0 < 4.11.1~pre.20180911.5acdd26fdc+dfsg-2 | 4.11.1~pre.20180911.5acdd26fdc+dfsg-2 |
| xen | xen | >= 0 < 4.11.1~pre.20180911.5acdd26fdc+dfsg-2 | 4.11.1~pre.20180911.5acdd26fdc+dfsg-2 |
CVSS provenance
nvdv3.06.5MEDIUMCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
nvdv2.04.9MEDIUMAV:L/AC:L/Au:N/C:N/I:N/A:C
osv6.5MEDIUM
vendor_debian6.5LOW
vendor_redhat6.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
xen: oxenstored does not apply quota-maxentity (XSA-272)
vendor_redhat·2018-08-14·CVSS 6.5
CVE-2018-15470 [MEDIUM] CWE-665 xen: oxenstored does not apply quota-maxentity (XSA-272)
xen: oxenstored does not apply quota-maxentity (XSA-272)
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.
Package: xen (Red Hat Enterprise Linux 5) - Not affected
Debian
CVE-2018-15470: xen - An issue was discovered in Xen through 4.11.x. The logic in oxenstored for handl...
vendor_debian·2018·CVSS 6.5
CVE-2018-15470 [MEDIUM] CVE-2018-15470: xen - An issue was discovered in Xen through 4.11.x. The logic in oxenstored for handl...
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.
Scope: local
bookworm: resolved (fixed in 4.11.1~pre.20180911.5acdd26fdc+dfsg-2)
bullseye: resolved (fixed in 4.11.1~pre.20180911.5acdd26fdc+dfsg-2)
forky: resolved (fixed in 4.11.1~pre.20180911.5acdd26f
GHSA
GHSA-9xrv-h87m-r2vc: An issue was discovered in Xen through 4
ghsa_unreviewed·2022-05-14
CVE-2018-15470 [MEDIUM] CWE-400 GHSA-9xrv-h87m-r2vc: An issue was discovered in Xen through 4
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.
OSV
CVE-2018-15470: An issue was discovered in Xen through 4
osv·2018-08-17·CVSS 6.5
CVE-2018-15470 [MEDIUM] CVE-2018-15470: An issue was discovered in Xen through 4
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.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2018-15470 xen: oxenstored does not apply quota-maxentity (XSA-272) [fedora-all]
bugzilla·2018-08-14·CVSS 6.5
CVE-2018-15470 [MEDIUM] CVE-2018-15470 xen: oxenstored does not apply quota-maxentity (XSA-272) [fedora-all]
CVE-2018-15470 xen: oxenstored does not apply quota-maxentity (XSA-272) [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported v
Bugzilla
CVE-2018-15470 xen: oxenstored does not apply quota-maxentity (XSA-272)
bugzilla·2018-07-31·CVSS 6.5
CVE-2018-15470 [MEDIUM] CVE-2018-15470 xen: oxenstored does not apply quota-maxentity (XSA-272)
CVE-2018-15470 xen: oxenstored does not apply quota-maxentity (XSA-272)
A flaw was found in xen. The logic in oxenstored for handling writes depended on the order of evaluation of expressions making up a tuple. The order of evaluation of subexpressions is not specified. This allows a malicious or buggy guest to write as many xenstore entriesas it wishes, causing unbounded memory usage in oxenstored. This can lead to a system-wide DoS.
Discussion:
Created xen tracking bugs for this issue:
Affects: fedora-all [bug 1616080]
http://xenbits.xen.org/xsa/advisory-272.htmlhttps://lists.debian.org/debian-lts-announce/2018/11/msg00013.htmlhttps://security.gentoo.org/glsa/201810-06http://xenbits.xen.org/xsa/advisory-272.htmlhttps://lists.debian.org/debian-lts-announce/2018/11/msg00013.htmlhttps://security.gentoo.org/glsa/201810-06
2018-08-17
Published