{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2020-24718 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-24718 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-24718 is a high-severity vulnerability in Freebsd Freebsd, published on 25 Sep 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-24718 and fix it if it is affected.\n\nWhat it is: CVE-2020-24718 is a high-severity vulnerability in Freebsd Freebsd, published on 25 Sep 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-24718 in the wild and no public exploit code.\n\nAffected product: Freebsd Freebsd. 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-24718/ (Markdown: https://insights.sbomify.com/CVE-2020-24718/index.md)","id":"CVE-2020-24718","markdown":"https://insights.sbomify.com/CVE-2020-24718/index.md","name":"CVE-2020-24718","record":{"aliases":["GHSA-g73j-h828-gg82"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"FreeBSD bhyve hypervisor","requires_auth":"high_privilege","summary":"A root user in a container can escalate privileges by modifying VMCS_HOST_RIP due to improper restriction of VMCS and VMCB operations in bhyve.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"freebsd","vendor":"freebsd"},{"product":"clustered_data_ontap","vendor":"netapp"},{"product":"omnios","vendor":"omniosce"},{"product":"openindiana","vendor":"openindiana"}],"cvss":{"score":8.2,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"bhyve, as used in FreeBSD through 12.1 and illumos (e.g., OmniOS CE through r151034 and OpenIndiana through Hipster 2020.04), does not properly restrict VMCS and VMCB read/write operations, as demonstrated by a root user in a container on an Intel system, who can gain privileges by modifying VMCS_HOST_RIP.","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":"Privilege escalation in n/a","id":"CVE-2020-24718","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"freebsd:freebsd","products":["freebsd:freebsd","netapp:clustered_data_ontap"],"type":"privilege_escalation","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2020-24719"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2020-24717"},"products":["n/a"],"published":"2020-09-25","related":[{"cvss_score":10,"headline":"Memory corruption in FreeBSD","id":"CVE-2018-17160","kev_date_added":null,"published":"2018-12-04"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2014-3954","kev_date_added":null,"published":"2014-10-27"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2006-4304","kev_date_added":null,"published":"2006-08-24"},{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2006-0226","kev_date_added":null,"published":"2006-01-19"},{"cvss_score":10,"headline":"Denial of service in n/a","id":"CVE-2004-0002","kev_date_added":null,"published":"2004-02-03"},{"cvss_score":10,"headline":"Security feature bypass in n/a","id":"CVE-2001-0969","kev_date_added":null,"published":"2002-03-09"},{"cvss_score":10,"headline":"Denial of service in n/a","id":"CVE-2001-0388","kev_date_added":null,"published":"2001-09-18"}],"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 root user in a container can escalate privileges by modifying VMCS_HOST_RIP due to improper restriction of VMCS and VMCB operations in bhyve.","url":"https://insights.sbomify.com/CVE-2020-24718/"}