Container operation redirection via identifier collision
Published Feb 7, 2020 · Updated Aug 6, 2024
Improper container identifier handling in Docker before 1.2 allows remote attackers to redirect ID-based operations via crafted names. The daemon accepts a user-supplied container name that collides with an existing container ID and resolves the name instead of that ID. Exploitation requires access to a Docker API endpoint that permits container creation; later ID-based actions can then affect the attacker-named container.
Summary
What happened
Improper container identifier handling in Docker before 1.2 allows remote attackers to redirect ID-based operations via crafted names. The daemon accepts a user-supplied container name that collides with an existing container ID and resolves the name instead of that ID. Exploitation requires access to a Docker API endpoint that permits container creation; later ID-based actions can then affect the attacker-named container.
The record
- CVE
- CVE-2014-5278
- Published
- Feb 7, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1036
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 7, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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
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