Privilege escalation via missing client verification
Published Jun 27, 2020 · Updated Aug 4, 2024
Privilege escalation in Docker Desktop 2.3.0.3 allows local users to gain elevated privileges via the com.docker.vmnetd helper. The helper accepts requests without verifying the calling client, allowing an unprivileged local process to invoke privileged operations. Local access is required; the documented consequence is elevation of privileges on the Docker Desktop host, with no evidence of remote reachability.
Summary
What happened
Privilege escalation in Docker Desktop 2.3.0.3 allows local users to gain elevated privileges via the com.docker.vmnetd helper. The helper accepts requests without verifying the calling client, allowing an unprivileged local process to invoke privileged operations. Local access is required; the documented consequence is elevation of privileges on the Docker Desktop host, with no evidence of remote reachability.
The record
- CVE
- CVE-2020-15360
- Published
- Jun 27, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-862, T1548
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 27, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- Docker Desktop CVE-2020-15360 privilege escalation proof of conceptproof of concept · unverified
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