Local ECI bypass via raw engine socket
Published Mar 13, 2023 · Updated Feb 27, 2025
Enhanced Container Isolation bypass in Docker Desktop 4.13.0 through 4.16.3 allows local users to launch containers without ECI hardening. The CLI honors -H or DOCKER_HOST values that select docker.raw.sock, or Windows' docker_engine_linux named pipe, without applying ECI restrictions. The bypass requires Docker Business with ECI enabled and affects only newly launched containers; it does not require local root or Administrator access.
Summary
What happened
Enhanced Container Isolation bypass in Docker Desktop 4.13.0 through 4.16.3 allows local users to launch containers without ECI hardening. The CLI honors -H or DOCKER_HOST values that select docker.raw.sock, or Windows' docker_engine_linux named pipe, without applying ECI restrictions. The bypass requires Docker Business with ECI enabled and affects only newly launched containers; it does not require local root or Administrator access.
The record
- CVE
- CVE-2023-0629
- Published
- Mar 13, 2023
- Updated
- Feb 27, 2025
- Vendor
- Docker
- Product
- Docker Desktop
- Classifications
- CWE-424, CWE-501, CAPEC-554, T1562.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 13, 2023CVE publishedPublication date reported by the CVE source.
- Feb 27, 2025Record 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=4.13.0 <4.17.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