{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15294 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-15294 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-15294 is a high-severity vulnerability in Bitdefender Hypervisor Introspection, published on 17 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-15294 and fix it if it is affected.\n\nWhat it is: CVE-2020-15294 is a high-severity vulnerability in Bitdefender Hypervisor Introspection, published on 17 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-15294 in the wild and no public exploit code.\n\nAffected product: Bitdefender Hypervisor Introspection. 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-15294/ (Markdown: https://insights.sbomify.com/CVE-2020-15294/index.md)","id":"CVE-2020-15294","markdown":"https://insights.sbomify.com/CVE-2020-15294/index.md","name":"CVE-2020-15294","record":{"aliases":["GHSA-mqrh-3j77-m2cw"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Hypervisor Introspection","requires_auth":"low_privilege","summary":"A race condition in Bitdefender Hypervisor Introspection allows arbitrary code execution via compiler optimization issues in memory-mapped guest space.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Bitdefender","cpe":[{"product":"hypervisor_introspection","vendor":"bitdefender"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-733","name":"Compiler Optimization Removal or Modification of Security-critical Code"}],"description":"Compiler Optimization Removal or Modification of Security-critical Code vulnerability in IntPeParseUnwindData() results in multiple dereferences to the same pointer. If the pointer is located in memory-mapped from the guest space, this may cause a race-condition where the generated code would dereference the same address twice, thus obtaining different values, which may lead to arbitrary code execution. This issue affects: Bitdefender Hypervisor Introspection versions prior to 1.132.2.","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":"Race condition in Hypervisor Introspection","id":"CVE-2020-15294","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Unused CVE for 2020","id":"CVE-2020-15295"},"packages":[],"prev":{"headline":"Memory corruption in Bitdefender Hypervisor Introspection (VA-9336)","id":"CVE-2020-15293"},"products":["Hypervisor Introspection"],"published":"2020-12-17","related":[{"cvss_score":6.1,"headline":"Memory corruption in Bitdefender Hypervisor Introspection (VA-9336)","id":"CVE-2020-15293","kev_date_added":null,"published":"2020-12-17"},{"cvss_score":5.5,"headline":"Lack of validation on data read from guest memory in Bitdefender HVI (VA-9333)","id":"CVE-2020-15292","kev_date_added":null,"published":"2020-12-17"}],"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-09-16","vendors":["Bitdefender"]},"summary":"A race condition in Bitdefender Hypervisor Introspection allows arbitrary code execution via compiler optimization issues in memory-mapped guest space.","url":"https://insights.sbomify.com/CVE-2020-15294/"}