ECI bypass via briefly accessible debug shell
Published Sep 25, 2023 · Updated Sep 24, 2024
Authorization bypass in Docker Desktop before 4.23.0 allows local users to evade ECI restrictions through a debug shell. The debug shell remains accessible briefly after launch instead of enforcing ECI restrictions against unprivileged users. Exploitation requires local unprivileged access, a Docker Business environment with ECI, and a version from 4.13.0 before 4.23.0.
Summary
What happened
Authorization bypass in Docker Desktop before 4.23.0 allows local users to evade ECI restrictions through a debug shell. The debug shell remains accessible briefly after launch instead of enforcing ECI restrictions against unprivileged users. Exploitation requires local unprivileged access, a Docker Business environment with ECI, and a version from 4.13.0 before 4.23.0.
The record
- CVE
- CVE-2023-5165
- Published
- Sep 25, 2023
- Updated
- Sep 24, 2024
- Vendor
- Docker
- Product
- Docker Desktop
- Classifications
- CWE-862, CWE-424, T1611
- Attack vector
- local
- 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=4.13.0 <4.23.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