{"api_version":"1","generated_at":"2026-04-23T09:39:06+00:00","cve":"CVE-2018-15470","urls":{"html":"https://cve.report/CVE-2018-15470","api":"https://cve.report/api/cve/CVE-2018-15470.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2018-15470","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2018-15470"},"summary":{"title":"CVE-2018-15470","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.","state":"PUBLIC","assigner":"cve@mitre.org","published_at":"2018-08-17 18:29:00","updated_at":"2018-11-13 11:29:00"},"problem_types":["CWE-400"],"metrics":[],"references":[{"url":"https://lists.debian.org/debian-lts-announce/2018/11/msg00013.html","name":"[debian-lts-announce] 20181112 [SECURITY] [DLA 1577-1] xen security update","refsource":"MLIST","tags":[],"title":"[SECURITY] [DLA 1577-1] xen security update","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://security.gentoo.org/glsa/201810-06","name":"GLSA-201810-06","refsource":"GENTOO","tags":["Third Party Advisory"],"title":"Xen: Multiple vulnerabilities (GLSA 201810-06) — Gentoo security","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"http://xenbits.xen.org/xsa/advisory-272.html","name":"http://xenbits.xen.org/xsa/advisory-272.html","refsource":"MISC","tags":["Vendor Advisory"],"title":"XSA-272 - Xen Security Advisories","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-15470","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-15470","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2018","cve_id":"15470","vulnerable":"1","versionEndIncluding":"4.11.0","cpe1":"cpe","cpe2":"2.3","cpe3":"o","cpe4":"xen","cpe5":"xen","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[{"cve":"CVE-2018-15470","qid":"500751","title":"Alpine Linux Security Update for xen"},{"cve":"CVE-2018-15470","qid":"504528","title":"Alpine Linux Security Update for xen"},{"cve":"CVE-2018-15470","qid":"710221","title":"Gentoo Linux Xen Multiple Vulnerabilities (GLSA 201810-06)"}]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"cve@mitre.org","ID":"CVE-2018-15470","STATE":"PUBLIC"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"n/a","version":{"version_data":[{"version_value":"n/a"}]}}]},"vendor_name":"n/a"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"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."}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"n/a"}]}]},"references":{"reference_data":[{"name":"GLSA-201810-06","refsource":"GENTOO","url":"https://security.gentoo.org/glsa/201810-06"},{"name":"[debian-lts-announce] 20181112 [SECURITY] [DLA 1577-1] xen security update","refsource":"MLIST","url":"https://lists.debian.org/debian-lts-announce/2018/11/msg00013.html"},{"name":"http://xenbits.xen.org/xsa/advisory-272.html","refsource":"MISC","url":"http://xenbits.xen.org/xsa/advisory-272.html"}]}},"nvd":{"publishedDate":"2018-08-17 18:29:00","lastModifiedDate":"2018-11-13 11:29:00","problem_types":["CWE-400"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.0","vectorString":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"CHANGED","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"HIGH","baseScore":6.5,"baseSeverity":"MEDIUM"},"exploitabilityScore":2,"impactScore":4},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:L/AC:L/Au:N/C:N/I:N/A:C","accessVector":"LOCAL","accessComplexity":"LOW","authentication":"NONE","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"COMPLETE","baseScore":4.9},"severity":"MEDIUM","exploitabilityScore":3.9,"impactScore":6.9,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:o:xen:xen:*:*:*:*:*:*:*:*","versionEndIncluding":"4.11.0","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2018","CveId":"15470","Ordinal":"132205","Title":"CVE-2018-15470","CVE":"CVE-2018-15470","Year":"2018"},"notes":[{"CveYear":"2018","CveId":"15470","Ordinal":"1","NoteData":"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.","Type":"Description","Title":null},{"CveYear":"2018","CveId":"15470","Ordinal":"2","NoteData":"2018-08-17","Type":"Other","Title":"Published"},{"CveYear":"2018","CveId":"15470","Ordinal":"3","NoteData":"2018-11-13","Type":"Other","Title":"Modified"}]}}}