Remote code execution via unsanitized source link
Published Oct 16, 2024 · Updated Oct 17, 2024
Remote code execution in Docker Desktop before 4.34.3 allows remote attackers to run code through a crafted GitHub source link in the Builds view. The Builds view consumes image-build source information without sanitizing its GitHub link before treating it as an actionable target; Docker has not disclosed the exact launch primitive. Exploitation requires a prepared source link, a reachable build record, and active user interaction, after which code runs with the Desktop application's host-user privileges.
Summary
What happened
Remote code execution in Docker Desktop before 4.34.3 allows remote attackers to run code through a crafted GitHub source link in the Builds view. The Builds view consumes image-build source information without sanitizing its GitHub link before treating it as an actionable target; Docker has not disclosed the exact launch primitive. Exploitation requires a prepared source link, a reachable build record, and active user interaction, after which code runs with the Desktop application's host-user privileges.
The record
- CVE
- CVE-2024-9348
- Published
- Oct 16, 2024
- Updated
- Oct 17, 2024
- Vendor
- Docker
- Product
- Docker Desktop
- Classifications
- CWE-20, CWE-116, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 16, 2024CVE publishedPublication date reported by the CVE source.
- Oct 17, 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 <4.34.3
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
No public exploit references are available in this record.
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