{"answers":{"affected":"3 open source packages ship an affected version, including py2play and Py2Play. It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-2875 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2005-2875 is a high-severity unsafe deserialization vulnerability in n/a, published on 13 Sep 2005. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2005-2875 and fix it if it is affected.\n\nWhat it is: CVE-2005-2875 is a high-severity unsafe deserialization vulnerability in n/a, published on 13 Sep 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2005-2875 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- py2play (PyPI): affected all versions up to 0.1.8; no fix listed\n- py2play (PyPI): affected all versions up to 0.1.8; no fix listed\n- Py2Play (PyPI): affected all versions up to 0.1.8; no fix listed\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-2005-2875/ (Markdown: https://insights.sbomify.com/CVE-2005-2875/index.md)","id":"CVE-2005-2875","markdown":"https://insights.sbomify.com/CVE-2005-2875/index.md","name":"CVE-2005-2875","record":{"aliases":["DSA-856-1","GHSA-wcpc-f63g-x26q","PYSEC-2026-742"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Python game library","requires_auth":"none","summary":"Remote attackers can execute arbitrary Python code in Py2Play by sending malicious pickled objects, requiring immediate library upgrades.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"py2play","vendor":"py2play"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Py2Play allows remote attackers to execute arbitrary Python code via pickled objects, which Py2Play unpickles and executes.","ecosystems":["PyPI"],"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":"Py2Play Unpickles Untrusted Objects","id":"CVE-2005-2875","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"deserialization","year":"2005"},"n_packages":3,"n_references":8,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2005-2876"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.1.8"],"package":"Py2Play","purl":null,"source":"GHSA-wcpc-f63g-x26q"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.1.8"],"package":"py2play","purl":"pkg:pypi/py2play","source":"GHSA-wcpc-f63g-x26q"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.1.8"],"package":"py2play","purl":"pkg:pypi/py2play","source":"PYSEC-2026-742"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2005-2874"},"products":["n/a"],"published":"2005-09-13","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":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary Python code in Py2Play by sending malicious pickled objects, requiring immediate library upgrades.","url":"https://insights.sbomify.com/CVE-2005-2875/"}