Code execution via unauthenticated executable downloads
Published Jan 2, 2020 · Updated Aug 6, 2024
Improper transport security in Docker Hub before 1.6.0 allows man-in-the-middle attackers to substitute executable downloads. Docker programs and scripts retrieve executable content and trust-signing keys over unauthenticated HTTP, then execute that content or rely on those keys to validate later downloads. An attacker positioned on the download path can replace both code and its trust material, enabling execution of attacker-controlled content.
Summary
What happened
Improper transport security in Docker Hub before 1.6.0 allows man-in-the-middle attackers to substitute executable downloads. Docker programs and scripts retrieve executable content and trust-signing keys over unauthenticated HTTP, then execute that content or rely on those keys to validate later downloads. An attacker positioned on the download path can replace both code and its trust material, enabling execution of attacker-controlled content.
The record
- CVE
- CVE-2014-0048
- Published
- Jan 2, 2020
- Updated
- Aug 6, 2024
- Vendor
- Docker
- Product
- Docker Hub
- Classifications
- CWE-20, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 2, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=before 1.6.0
What conditions does exploitation require?
What is affected?
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
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