{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-2025 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-2025 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-2025 is a high-severity vulnerability in Kata Containers, published on 19 May 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-2025 and fix it if it is affected.\n\nWhat it is: CVE-2020-2025 is a high-severity vulnerability in Kata Containers, published on 19 May 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-2025 in the wild and no public exploit code.\n\nAffected product: Kata Containers. 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-2025/ (Markdown: https://insights.sbomify.com/CVE-2020-2025/index.md)","id":"CVE-2020-2025","markdown":"https://insights.sbomify.com/CVE-2020-2025/index.md","name":"CVE-2020-2025","record":{"aliases":[],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Kata Containers","requires_auth":"low_privilege","summary":"A malicious guest VM can overwrite the host image file to compromise subsequent guest VMs, allowing privilege escalation and code execution.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"palo_alto","cpe":[{"product":"runtime","vendor":"katacontainers"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-281","name":"Improper Preservation of Permissions"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"Kata Containers before 1.11.0 on Cloud Hypervisor persists guest filesystem changes to the underlying image file on the host. A malicious guest can overwrite the image file to gain control of all subsequent guest VMs. Since Kata Containers uses the same VM image file with all VMMs, this issue may also affect QEMU and Firecracker based guests.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Kata Containers - Cloud Hypervisor guests persist filesystem changes to the underlying host image file","id":"CVE-2020-2025","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Kata Containers - Guests can trick the kata-runtime into mounting the container image on any host path","id":"CVE-2020-2026"},"packages":[],"prev":{"headline":"Kata Containers - Guests can trick the kata-runtime into unmounting any mount point on the host","id":"CVE-2020-2024"},"products":["Kata Containers"],"published":"2020-05-19","related":[{"cvss_score":6.5,"headline":"Kata Containers - Guests can trick the kata-runtime into unmounting any mount point on the host","id":"CVE-2020-2024","kev_date_added":null,"published":"2020-05-19"},{"cvss_score":3.8,"headline":"Kata Containers - Containers have access to the guest root filesystem device","id":"CVE-2020-2023","kev_date_added":null,"published":"2020-06-10"}],"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":["Kata Containers"]},"summary":"A malicious guest VM can overwrite the host image file to compromise subsequent guest VMs, allowing privilege escalation and code execution.","url":"https://insights.sbomify.com/CVE-2020-2025/"}