Host code execution via exposed extension IPC
Published Jul 9, 2024 · Updated Aug 1, 2024
Privilege escalation in Docker Desktop before 4.29.0 allows local users in its VM to execute arbitrary code on the host via extension IPC. The extension-manager exposes a dangerous Docker Extensions function to extension and dashboard IPC messages instead of restricting communication to intended endpoints. Exploitation requires prior high-privileged code execution after a container breakout, Docker Extensions enabled, and the Marketplace-only setting disabled.
Summary
What happened
Privilege escalation in Docker Desktop before 4.29.0 allows local users in its VM to execute arbitrary code on the host via extension IPC. The extension-manager exposes a dangerous Docker Extensions function to extension and dashboard IPC messages instead of restricting communication to intended endpoints. Exploitation requires prior high-privileged code execution after a container breakout, Docker Extensions enabled, and the Marketplace-only setting disabled.
The record
- CVE
- CVE-2024-6222
- Published
- Jul 9, 2024
- Updated
- Aug 1, 2024
- Vendor
- Docker
- Product
- Docker Desktop
- Classifications
- CWE-923, CAPEC-480, T1611
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jul 9, 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 <4.29.0
- Affected versionversion=0 <v4.29.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