{"answers":{"affected":"3 open source packages ship an affected version, including pyo3. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-35917 in the wild and no public exploit code.","fix":"Upgrade pyo3 to 0.12.4 or later.","what":"CVE-2020-35917 is a medium-severity use after free vulnerability in n/a, published on 31 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-35917 and fix it if it is affected.\n\nWhat it is: CVE-2020-35917 is a medium-severity use after free vulnerability in n/a, published on 31 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-35917 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pyo3 (crates.io): affected from 0.12.0; fixed in 0.12.4\n- pyo3 (crates.io): affected from 0.12.0; fixed in 0.12.4\n- pyo3 (crates.io): affected from 0.12.0; fixed in 0.12.4\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-35917/ (Markdown: https://insights.sbomify.com/CVE-2020-35917/index.md)","id":"CVE-2020-35917","markdown":"https://insights.sbomify.com/CVE-2020-35917/index.md","name":"CVE-2020-35917","record":{"aliases":["GHSA-2vx6-fcw6-hpr6","RUSTSEC-2020-0074"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rust Python bindings","requires_auth":"low_privilege","summary":"A use-after-free vulnerability in the pyo3 Rust crate allows attackers to potentially execute arbitrary code or cause a denial of service.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pyo3","vendor":"pyo3_project"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"An issue was discovered in the pyo3 crate before 0.12.4 for Rust. There is a reference-counting error and use-after-free in From\u003cPy\u003cT\u003e\u003e.","ecosystems":["crates.io"],"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":"Reference counting error in pyo3","id":"CVE-2020-35917","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"use_after_free","year":"2020"},"n_packages":3,"n_references":1,"next":{"headline":"Unexpected panic when decoding tokens in branca","id":"CVE-2020-35918"},"packages":[{"ecosystem":"crates.io","fixed":["0.12.4"],"introduced":["0.12.0"],"last_affected":[],"package":"pyo3","purl":null,"source":"GHSA-2vx6-fcw6-hpr6"},{"ecosystem":"crates.io","fixed":["0.12.4"],"introduced":["0.12.0"],"last_affected":[],"package":"pyo3","purl":"pkg:cargo/pyo3","source":"GHSA-2vx6-fcw6-hpr6"},{"ecosystem":"crates.io","fixed":["0.12.4"],"introduced":["0.12.0"],"last_affected":[],"package":"pyo3","purl":"pkg:cargo/pyo3","source":"RUSTSEC-2020-0074"}],"prev":{"headline":"Mutable reference with immutable provenance in image","id":"CVE-2020-35916"},"products":["n/a"],"published":"2020-12-31","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"},{"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 use-after-free vulnerability in the pyo3 Rust crate allows attackers to potentially execute arbitrary code or cause a denial of service.","url":"https://insights.sbomify.com/CVE-2020-35917/"}