CVE-2018-15470
Published: 17 August 2018
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.
Notes
Author | Note |
---|---|
mdeslaur | hypervisor packages are in universe. For issues in the hypervisor, add appropriate tags to each section, ex: Tags_xen: universe-binary |
Priority
Status
Package | Release | Status |
---|---|---|
xen Launchpad, Ubuntu, Debian |
bionic |
Needed
|
cosmic |
Ignored
(end of life)
|
|
disco |
Ignored
(end of life)
|
|
eoan |
Ignored
(end of life)
|
|
focal |
Not vulnerable
(4.11.1~pre.20180911.5acdd26fdc+dfsg-2)
|
|
groovy |
Ignored
(end of life)
|
|
hirsute |
Ignored
(end of life)
|
|
impish |
Ignored
(end of life)
|
|
jammy |
Not vulnerable
(4.11.1~pre.20180911.5acdd26fdc+dfsg-2)
|
|
kinetic |
Not vulnerable
(4.11.1~pre.20180911.5acdd26fdc+dfsg-2)
|
|
lunar |
Not vulnerable
(4.11.1~pre.20180911.5acdd26fdc+dfsg-2)
|
|
mantic |
Not vulnerable
(4.11.1~pre.20180911.5acdd26fdc+dfsg-2)
|
|
trusty |
Does not exist
(trusty was needs-triage)
|
|
upstream |
Released
(4.11.1~pre.20180911.5acdd26fdc+dfsg-2)
|
|
xenial |
Needed
|
|
Binaries built from this source package are in Universe and so are supported by the community. |
Severity score breakdown
Parameter | Value |
---|---|
Base score | 6.5 |
Attack vector | Local |
Attack complexity | Low |
Privileges required | Low |
User interaction | None |
Scope | Changed |
Confidentiality | None |
Integrity impact | None |
Availability impact | High |
Vector | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H |