vulnwire
6.5med

CVE-2018-15470

An issue was discovered in Xen through 4.11.x.

Published 8 y ago · modified 4 mo ago · JSON

CVSS
6.5
v3.0 · NVD
CISA KEV
No
not known exploited
EPSS
0.4%
percentile 34%
Public exploits
0
none known

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.

Exploit prediction (EPSS)

0.40% probability of exploitation in the next 30 days, higher than 34% of all scored CVEs.

CVSS scores

Assigned byVersionScoreVector
NVD3.06.5CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
NVD2.04.9AV:L/AC:L/Au:N/C:N/I:N/A:C

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

References

  • security.gentoo.org /glsa/201810-06 · vendor-advisory, x_refsource_GENTOO, x_transferred
  • lists.debian.org /debian-lts-announce/2018/11/msg00013.html · mailing-list, x_refsource_MLIST, x_transferred
  • xenbits.xen.org /xsa/advisory-272.html · x_refsource_MISC, x_transferred

Sources

vulnwire keeps one entry per vulnerability: the CVE id wins, then GHSA; records that alias each other are merged. Machine-readable: JSON.