{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-29487 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-29487 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-29487 is a high-severity denial of service vulnerability in n/a, published on 15 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-29487 and fix it if it is affected.\n\nWhat it is: CVE-2020-29487 is a high-severity denial of service vulnerability in n/a, published on 15 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-29487 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-29487/ (Markdown: https://insights.sbomify.com/CVE-2020-29487/index.md)","id":"CVE-2020-29487","markdown":"https://insights.sbomify.com/CVE-2020-29487/index.md","name":"CVE-2020-29487","record":{"aliases":["GHSA-q329-j6wm-vf6q"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Xen XAPI toolstack","requires_auth":"none","summary":"A malicious guest can cause host denial of service by monopolizing memory in dom0 through inefficient xenstore key watching logic in the XAPI toolstack.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"xapi","vendor":"xen"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"An issue was discovered in Xen XAPI before 2020-12-15. Certain xenstore keys provide feedback from the guest, and are therefore watched by toolstack. Specifically, keys are watched by xenopsd, and data are forwarded via RPC through message-switch to xapi. The watching logic in xenopsd sends one RPC update containing all data, any time any single xenstore key is updated, and therefore has O(N^2) time complexity. Furthermore, message-switch retains recent (currently 128) RPC messages for diagnostic purposes, yielding O(M*N) space complexity. The quantity of memory a single guest can monopolise is bounded by xenstored quota, but the quota is fairly large. It is believed to be in excess of 1G per malicious guest. In practice, this manifests as a host denial of service, either through message-switch thrashing against swap, or OOMing entirely, depending on dom0's configuration. (There are no quotas in xenopsd to limit the quantity of keys that result in RPC traffic.) A buggy or malicious guest can cause unreasonable memory usage in dom0, resulting in a host denial of service. All versions of XAPI are vulnerable. Systems that are not using the XAPI toolstack are not vulnerable.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Denial of service in n/a","id":"CVE-2020-29487","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Unity","id":"CVE-2020-29489"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2020-29486"},"products":["n/a"],"published":"2020-12-15","related":[{"cvss_score":5.3,"headline":"Denial of service in Xapi","id":"CVE-2022-33749","kev_date_added":null,"published":"2022-10-11"},{"cvss_score":3.8,"headline":"Xapi: Metadata injection attack against backup/restore functionality","id":"CVE-2024-31144","kev_date_added":null,"published":"2025-02-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"A malicious guest can cause host denial of service by monopolizing memory in dom0 through inefficient xenstore key watching logic in the XAPI toolstack.","url":"https://insights.sbomify.com/CVE-2020-29487/"}