CVE-2024-40624
Deserialization of untrusted data in torrentpier/torrentpier
Vexday Risk Score
28Low
SSVC decision (CISA)
Track
No exploitation signal → monitor
CVSS 9.8EPSS 1.0%KEV nãoPoC —Nuclei —Metasploit —Patch —
Lifecycle
15 Jul 2024Published on NVD
Recommendation: Monitor — no exploitation signal at the moment.
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected products
torrentpier · torrentpierWant to know if your infrastructure is exposed to this?
Talk to TrueHacking →References
https://github.com/torrentpier/torrentpier/blob/84f6c9f4a081d9ffff4c233098758280304bf50f/library/includes/functions.php#L41-L60https://github.com/torrentpier/torrentpier/commit/ed37e6e522f345f2b46147c6f53c1ab6dec1db9ehttps://github.com/torrentpier/torrentpier/security/advisories/GHSA-fg86-4c2r-7wxw