qdrant is vulnerable to path traversal due to improper input validation in the `/collections/{name}/snapshots/upload` endpoint
CVE-2024-3584 · GHSA-xcr2-h8hv-6227 · published 2024-06-02
- Severity
- Critical
- CVSS score
- 9.8
- Chance of exploitation (EPSS)
- 0.55%
- Fixed in
- 1.9.0
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Total
- CISA SSVC
qdrant/qdrant version 1.9.0-dev is vulnerable to path traversal due to improper input validation in the /collections/{name}/snapshots/upload endpoint. This vulnerability allows for the writing and overwriting of arbitrary files on the server, potentially leading to a full takeover of the system. The issue is fixed in version 1.9.0.
Upgrade qdrant to 1.9.0 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| qdrant | crates.io | = 1.9.0-dev | 1.9.0 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
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.