Remote code execution via snapshot path traversal
Published Apr 10, 2024 · Updated Aug 1, 2024
Path traversal in Qdrant before 1.9.0 allows remote attackers to overwrite arbitrary server files through a snapshot upload. The collection snapshot upload handler accepts the snapshot parameter as a filesystem path without confining the resolved destination to its upload directory. Self-hosted deployments without API-key protection expose the write remotely; Qdrant Cloud requires authentication and its read-only filesystem limits impact to a cluster crash.
Summary
What happened
Path traversal in Qdrant before 1.9.0 allows remote attackers to overwrite arbitrary server files through a snapshot upload. The collection snapshot upload handler accepts the snapshot parameter as a filesystem path without confining the resolved destination to its upload directory. Self-hosted deployments without API-key protection expose the write remotely; Qdrant Cloud requires authentication and its read-only filesystem limits impact to a cluster crash.
The record
- CVE
- CVE-2024-2221
- Published
- Apr 10, 2024
- Updated
- Aug 1, 2024
- Vendor
- Qdrant
- Product
- Qdrant
- Classifications
- CWE-434, CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 10, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.8.0
- Affected versionversion=unspecified <1.8.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- huntr snapshot-upload path traversal proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo