Allegro AI ClearML path traversal vulnerability
CVE-2024-24591 · GHSA-m95h-p4gg-wfw3 · published 2024-02-06 · updated 2024-02-16
- Severity
- High
- CVSS score
- 8.8
- Chance of exploitation (EPSS)
- 0.80%
- Fixed in
- No fix yet
- Exploitation Public proof of concept
- Automatable No
- Technical impact Total
- CISA SSVC
A path traversal vulnerability in versions 1.4.0 to 1.14.1 of the client SDK of Allegro AI’s ClearML platform enables a maliciously uploaded dataset to write local or remote files to an arbitrary location on an end user’s system when interacted with.
No fixed release is listed yet for clearml. Follow the source advisory for updates, and until one ships:
General guidance from ShieldPi, not a vendor fix
- Path traversal. Limit the folders it can reach at the operating-system level, such as a container or a user with access to only those folders, and keep credentials and keys outside them.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| clearml | PyPI | >= 0.17.0, <= 1.14.1 | No fix yet |
- CriticalMCP Path Traversal Allows Full-Filesystem Read and JWT Secret Exfiltration Leading to Account Takeoverlangflow, langflow-base
- Critical@zereight/mcp-gitlab: Unauthenticated arbitrary file read via `upload_markdown` enables PAT exfiltration and full account takeover@zereight/mcp-gitlab
- CriticalFlowise RCE via SQL Database Chain Nodeflowise, flowise-components
- CriticalLangroid: SQLChatAgent dangerous-function blocklist can be bypassed with quoted or schema-qualified pg_read_file callslangroid
- Criticalfast-mcp-telegram: Bearer token path traversal bypasses reserved Telegram session protectionfast-mcp-telegram
- CriticalMCP Toolbox HTTP tool path parameters allow traversal to unintended endpointsgithub.com/googleapis/mcp-toolbox
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.