Local privilege escalation via TOCTOU symlink overwrite
Published Apr 27, 2023 · Updated Jan 31, 2025
File overwrite in Docker Desktop for Windows before 4.6 allows local users to replace arbitrary host files through dockerBackendV2. The windowscontainers/start API accepts an attacker-controlled data-root value and accesses local-kv.db through a path that can be replaced with a symlink between validation and use. Exploitation requires low-privilege local access and winning the race; overwriting a privileged file enables privilege escalation.
Summary
What happened
File overwrite in Docker Desktop for Windows before 4.6 allows local users to replace arbitrary host files through dockerBackendV2. The windowscontainers/start API accepts an attacker-controlled data-root value and accesses local-kv.db through a path that can be replaced with a symlink between validation and use. Exploitation requires low-privilege local access and winning the race; overwriting a privileged file enables privilege escalation.
The record
- CVE
- CVE-2022-38730
- Published
- Apr 27, 2023
- Updated
- Jan 31, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-59, CWE-367, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 27, 2023CVE publishedPublication date reported by the CVE source.
- Jan 31, 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?
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.
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