# CVE-2024-40624: Deserialization of untrusted data in torrentpier/torrentpier

> Attackers can achieve remote code execution by sending malicious serialized data in cookies to the TorrentPier web application.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-fg86-4c2r-7wxw

## What is CVE-2024-40624?

CVE-2024-40624 is a critical unsafe deserialization vulnerability in torrentpier, published on 15 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TorrentPier is an open source BitTorrent Public/Private tracker engine, written in php. In `torrentpier/library/includes/functions.php`, `get_tracks()` uses the unsafe native PHP serialization format to deserialize user-controlled cookies. One can use phpggc and the chain Guzzle/FW1 to write PHP code to an arbitrary file, and execute commands on the system. For instance, the cookie bb_t will be deserialized when browsing to viewforum.php. This issue has been addressed in commit `ed37e6e52` which is expected to be included in release version 2.4.4. Users are advised to upgrade as soon as the new release is available. There are no known workarounds for this vulnerability.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2024-40624?

2 open source packages ship an affected version, including torrentpier/torrentpier.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `torrentpier/torrentpier` | Packagist | All versions | 2.4.4 |
| `torrentpier/torrentpier` | Packagist | All versions | 2.4.4 |

## How do I fix CVE-2024-40624?

Upgrade torrentpier/torrentpier to 2.4.4 or later.

## Is CVE-2024-40624 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-40624 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-40624 and fix it if it is affected.

What it is: CVE-2024-40624 is a critical unsafe deserialization vulnerability in torrentpier, published on 15 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-40624 exists.

Affected packages and fixed versions:
- torrentpier/torrentpier (Packagist): affected all versions; fixed in 2.4.4
- torrentpier/torrentpier (Packagist): affected all versions; fixed in 2.4.4

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-2024-40624/ (Markdown: https://insights.sbomify.com/CVE-2024-40624/index.md)
```

## Sources

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

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