{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-2713 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-2713 is a medium-severity vulnerability in Google gVisor, published on 28 Mar 2025. 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-2025-2713 and fix it if it is affected.\n\nWhat it is: CVE-2025-2713 is a medium-severity vulnerability in Google gVisor, published on 28 Mar 2025. 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-2025-2713 in the wild and no public exploit code.\n\nAffected product: Google gVisor. 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-2025-2713/ (Markdown: https://insights.sbomify.com/CVE-2025-2713/index.md)","id":"CVE-2025-2713","markdown":"https://insights.sbomify.com/CVE-2025-2713/index.md","name":"CVE-2025-2713","record":{"aliases":["DEBIAN-CVE-2025-2713","GHSA-4fj4-9m67-3mj3","UBUNTU-CVE-2025-2713"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["privilege_escalation","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"gVisor container runtime","requires_auth":"low_privilege","summary":"Unprivileged users can escalate privileges and read restricted files in gVisor runsc due to improper permission handling during process initialization.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Google","cpe":[{"product":"gvisor","vendor":"google"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-266","name":"Incorrect Privilege Assignment"}],"description":"Google gVisor's runsc component exhibited a local privilege escalation vulnerability due to incorrect handling of file access permissions, which allowed unprivileged users to access restricted files. This occurred because the process initially ran with root-like permissions until the first fork.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Improper File Permission Handling in Google gVisor runsc","id":"CVE-2025-2713","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"JoomlaUX JUX Real Estate addagent cross site scripting","id":"CVE-2025-2714"},"packages":[],"prev":{"headline":"Yonyou UFIDA ERP-NC top.jsp cross site scripting","id":"CVE-2025-2712"},"products":["gVisor"],"published":"2025-03-28","related":[{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2018-19333","kev_date_added":null,"published":"2018-11-17"},{"cvss_score":6.8,"headline":"Path traversal in n/a","id":"CVE-2018-16359","kev_date_added":null,"published":"2018-09-02"},{"cvss_score":6.3,"headline":"Improved Seeding and Hashing In gVisor","id":"CVE-2024-10026","kev_date_added":null,"published":"2025-01-30"},{"cvss_score":6.3,"headline":"Information disclosure in gVisor","id":"CVE-2024-10603","kev_date_added":null,"published":"2025-01-30"},{"cvss_score":5.5,"headline":"Denial of service in n/a","id":"CVE-2018-20168","kev_date_added":null,"published":"2018-12-17"},{"cvss_score":4.8,"headline":"Denial-of-Service in Gvisor","id":"CVE-2023-7258","kev_date_added":null,"published":"2024-05-15"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-08","vendors":["Google"]},"summary":"Unprivileged users can escalate privileges and read restricted files in gVisor runsc due to improper permission handling during process initialization.","url":"https://insights.sbomify.com/CVE-2025-2713/"}