Code execution via crafted extension metadata
Published Sep 25, 2023 · Updated Sep 24, 2024
Code injection in Docker Desktop before 4.12.0 allows remote authenticated users to execute code through a malicious extension. The Desktop extension interface renders a crafted description or changelog without safely neutralizing executable content, allowing it to escape the display context. Exploitation requires interaction with the malicious extension; successful code runs in the Docker Desktop application context on Windows, macOS, or Linux.
Summary
What happened
Code injection in Docker Desktop before 4.12.0 allows remote authenticated users to execute code through a malicious extension. The Desktop extension interface renders a crafted description or changelog without safely neutralizing executable content, allowing it to escape the display context. Exploitation requires interaction with the malicious extension; successful code runs in the Docker Desktop application context on Windows, macOS, or Linux.
The record
- CVE
- CVE-2023-0625
- Published
- Sep 25, 2023
- Updated
- Sep 24, 2024
- Vendor
- Docker
- Product
- Docker Desktop
- Classifications
- CWE-79, CWE-829, CWE-94, CAPEC-253, CAPEC-63, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 25, 2023CVE publishedPublication date reported by the CVE source.
- Sep 24, 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.12.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
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