Local protected-data access via undisclosed access-control flaw
Published May 25, 2022 · Updated Aug 4, 2024
Incorrect access control in Docker Desktop 4.3.0 allows local users to read and modify protected data via unspecified vectors. Docker and MITRE have not published the affected component or the access-control operation that mishandles local input. Exploitation requires local low-privileged access; the published impact covers confidentiality and integrity, with no reported service interruption.
Summary
What happened
Incorrect access control in Docker Desktop 4.3.0 allows local users to read and modify protected data via unspecified vectors. Docker and MITRE have not published the affected component or the access-control operation that mishandles local input. Exploitation requires local low-privileged access; the published impact covers confidentiality and integrity, with no reported service interruption.
The record
- CVE
- CVE-2021-44719
- Published
- May 25, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 25, 2022CVE 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.
Weakness, pattern, technique
No sourced classifications are available.
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