Docker Desktop before 4.17.0 allows an unprivileged user to bypass Enhanced Container Isolation restrictions via the raw Docker socket and launch privileged containers
Docker Desktop before 4.17.0 allows an unprivileged user to bypass Enhanced Container Isolation (ECI) restrictions by setting the Docker host to docker.raw.sock, or npipe:////.pipe/docker_engine_linux on Windows, via the -H (--host) CLI flag or the DOCKER_HOST environment variable and launch containers without the additional hardening features provided by ECI. This would not affect already running containers, nor containers launched through the usual approach (without Docker's raw socket).
The affected functionality is available for Docker Business customers only and assumes an environment where users are not granted local root or Administrator privileges.
This issue has been fixed in Docker Desktop 4.17.0.
Affected Docker Desktop versions: from 4.13.0 before 4.17.0.
Problem Types
| Type | CWE ID | Description |
|---|
| CWE | CWE-424 | CWE-424: Improper Protection of Alternate Path |
| CWE | CWE-501 | CWE-501: Trust Boundary Violation |
Type: CWE
Description: CWE-424: Improper Protection of Alternate Path
Type: CWE
Description: CWE-501: Trust Boundary Violation
Metrics
| Version | Base score | Base severity | Vector |
|---|
| 3.1 | 7.1 | HIGH | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
Version: 3.1
Base score: 7.1
Base severity: HIGH
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Impacts
| CAPEC ID | Description |
|---|
| CAPEC-554 | CAPEC-554 Functionality Bypass |
Description: CAPEC-554 Functionality Bypass