CVE-2024-1651
Published: 20 February 2024
Summary
CVE-2024-1651 is a critical-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Torrentpier Torrentpier. Its CVSS base score is 10.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 0.8% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
Torrentpier version 2.4.1 is affected by an insecure deserialization vulnerability (CWE-502) that permits execution of arbitrary commands on the underlying server. The flaw received a CVSS 3.1 score of 10.0, reflecting network attack vector, low complexity, no required privileges or user interaction, and full impact on confidentiality, integrity, and availability with a changed scope.
An unauthenticated remote attacker can supply a malicious serialized object to the application and achieve arbitrary code execution, resulting in complete server compromise. The high EPSS score of 0.8059 indicates substantial exploitation likelihood.
Public references point to detailed analysis from Fluid Attacks and the Torrentpier GitHub repository, though no specific patch or mitigation guidance is stated in the available data.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-0524
Vulnerability details
Torrentpier version 2.4.1 allows executing arbitrary commands on the server. This is possible because the application is vulnerable to insecure deserialization.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
CVE-2024-1651 is an insecure deserialization vulnerability in the public-facing web application Torrentpier 2.4.1 that allows remote unauthenticated arbitrary command execution (RCE).
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Penetration testing supplies malicious serialized objects, detecting unsafe deserialization and supporting corrective actions.
Evaluation of untrusted data handling (deserialization testing) reveals unsafe processing, which the required remediation process addresses.
Untrusted serialized data can be deserialized and observed inside the chamber, blocking gadget-chain exploitation outside the sandbox.
Validates or rejects untrusted serialized data before deserialization occurs.
Identifies and blocks malicious code introduced through deserialization of untrusted data at system boundaries.
Integrity verification of serialized information can detect tampering before deserialization occurs.
Provenance of associated data allows detection of untrusted sources before deserialization or processing occurs.