# CVE-2005-2875: Py2Play Unpickles Untrusted Objects

> Remote attackers can execute arbitrary Python code in Py2Play by sending malicious pickled objects, requiring immediate library upgrades.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Sep 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-856-1, GHSA-wcpc-f63g-x26q, PYSEC-2026-742

## What is CVE-2005-2875?

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.

### Official description

Py2Play allows remote attackers to execute arbitrary Python code via pickled objects, which Py2Play unpickles and executes.

## Which versions are affected by CVE-2005-2875?

3 open source packages ship an affected version, including py2play and Py2Play. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `py2play` | PyPI | All versions to 0.1.8 | None |
| `py2play` | PyPI | All versions to 0.1.8 | None |
| `Py2Play` | PyPI | All versions to 0.1.8 | None |

Products: Py2play Py2play.

## How do I fix CVE-2005-2875?

Upgrade to a fixed version.

## Is CVE-2005-2875 being exploited?

There is no known exploitation of CVE-2005-2875 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2875 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2005-2875 in the wild and no public exploit code.

Affected packages and fixed versions:
- py2play (PyPI): affected all versions up to 0.1.8; no fix listed
- py2play (PyPI): affected all versions up to 0.1.8; no fix listed
- Py2Play (PyPI): affected all versions up to 0.1.8; no fix listed

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2005-2875/ (Markdown: https://insights.sbomify.com/CVE-2005-2875/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2005-2875
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2005-2875
- OSV: https://osv.dev/vulnerability/CVE-2005-2875

---
From sbomify Insights: https://insights.sbomify.com/CVE-2005-2875/
Summaries are generated and may contain mistakes; the official description above is the record.