{"answers":{"affected":"2 open source packages ship an affected version, including torrentpier/torrentpier.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-40624 exists.","fix":"Upgrade torrentpier/torrentpier to 2.4.4 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2024-40624 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-40624 exists.\n\nAffected packages and fixed versions:\n- torrentpier/torrentpier (Packagist): affected all versions; fixed in 2.4.4\n- torrentpier/torrentpier (Packagist): affected all versions; fixed in 2.4.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-2024-40624/ (Markdown: https://insights.sbomify.com/CVE-2024-40624/index.md)","id":"CVE-2024-40624","markdown":"https://insights.sbomify.com/CVE-2024-40624/index.md","name":"CVE-2024-40624","record":{"aliases":["GHSA-fg86-4c2r-7wxw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"BitTorrent tracker engine","requires_auth":"none","summary":"Attackers can achieve remote code execution by sending malicious serialized data in cookies to the TorrentPier web application.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"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.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Deserialization of untrusted data in torrentpier/torrentpier","id":"CVE-2024-40624","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"deserialization","year":"2024"},"n_packages":2,"n_references":3,"next":{"headline":"GeoServer Coverage REST API Allows Server Side Request Forgery","id":"CVE-2024-40625"},"packages":[{"ecosystem":"Packagist","fixed":["2.4.4"],"introduced":["0"],"last_affected":[],"package":"torrentpier/torrentpier","purl":null,"source":"GHSA-fg86-4c2r-7wxw"},{"ecosystem":"Packagist","fixed":["2.4.4"],"introduced":["0"],"last_affected":[],"package":"torrentpier/torrentpier","purl":"pkg:composer/torrentpier/torrentpier","source":"GHSA-fg86-4c2r-7wxw"}],"prev":{"headline":"Rockwell Automation Pavilion8® Unencrypted Data Vulnerability via HTTP protocol","id":"CVE-2024-40620"},"products":["torrentpier"],"published":"2024-07-15","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["torrentpier"]},"summary":"Attackers can achieve remote code execution by sending malicious serialized data in cookies to the TorrentPier web application.","url":"https://insights.sbomify.com/CVE-2024-40624/"}