CVE-2024-6222·Docker vulnerability
In Docker Desktop before v4.29.0, an attacker who has gained access to the Docker Desktop VM through a container breakout can further escape to the host by passing extensions and dashboard related IPC messages. Docker Desktop v4.29.0 https://docs.docker.com/desktop/release-notes/#4290 fixes the issue on MacOS, Linux and Windows with Hyper-V backend. As exploitation requires "Allow only extensions distributed through the Docker Marketplace" to be disabled, Docker Desktop v4.31.0 https://docs.docker.com/desktop/release-notes/#4310 additionally changes the default configuration to enable this setting by default.
- Severity
- high
- Software
- Docker
- Fixed in
- 4.29.0
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 2.3% — higher than 85% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Affected versions
Until: 4.29.0
Fixed in: 4.29.0
How to fix this CVE
Update Docker Desktop to version 4.29.0 or later to patch the container-to-host escape vulnerability affecting the IPC message handling system. Additionally, upgrade to Docker Desktop v4.31.0 or newer to benefit from the hardened default configuration that restricts unsigned extensions, which reduces the attack surface for this vulnerability class.
sudo dnf upgrade docker-ceDefensia detects this vulnerability
How to check if you are affected
- Run 'docker --version' to confirm your current Docker version and compare against 4.29.0
- Check 'docker info' output and verify the Server Version field; if below 4.29.0, the system is vulnerable
- Inspect Docker daemon logs at '/var/lib/docker/containers/*/json.log' for unusual IPC communication patterns or extension-related errors
- After patching, re-run 'docker --version' and confirm the version is 4.29.0 or higher; then restart Docker daemon with 'sudo systemctl restart docker'
FAQ
What is CVE-2024-6222?
CVE-2024-6222 is a privilege escalation vulnerability in Docker Desktop that allows an attacker who has already escaped from a container to further break out to the host system by exploiting improper validation of IPC (inter-process communication) messages used by Docker extensions and the dashboard.
Is CVE-2024-6222 being actively exploited?
No, CVE-2024-6222 is not currently listed on CISA's Known Exploited Vulnerabilities catalog, and no public exploits are available. However, the vulnerability requires significant pre-existing access (container breakout), so real-world exploitation risk depends on your container security posture.
What versions of Docker are affected by CVE-2024-6222?
All versions of Docker Desktop prior to 4.29.0 are vulnerable, regardless of operating system (macOS, Linux, Windows with Hyper-V backend).
How do I check if my server is vulnerable to CVE-2024-6222?
Run 'docker --version' and check if the reported version is below 4.29.0. On Docker Desktop, also verify that 'Allow only extensions distributed through the Docker Marketplace' is enabled in Settings > Extensions to confirm the default hardening is active.
Does Defensia detect CVE-2024-6222?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Docker is installed on a monitored server, CVE-2024-6222 will appear in your dashboard with remediation steps.
Related Docker CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-6222. Free for 1 server.
Get started free