First published: Mon Nov 17 2014(Updated: )
Docker before 1.3.1 and docker-py before 0.5.3 fall back to HTTP when the HTTPS connection to the registry fails, which allows man-in-the-middle attackers to conduct downgrade attacks and obtain authentication and image data by leveraging a network position between the client and the registry to block HTTPS traffic.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
go/github.com/docker/docker | <1.3.1 | 1.3.1 |
Docker | <=1.3.0 | |
Docker | <=0.5.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-5277 has been classified as a moderate severity vulnerability due to the potential for man-in-the-middle attacks.
To resolve CVE-2014-5277, upgrade Docker to version 1.3.1 or higher and docker-py to version 0.5.3 or higher.
CVE-2014-5277 affects Docker versions prior to 1.3.1 and docker-py versions prior to 0.5.3.
CVE-2014-5277 exploits the fallback to HTTP when HTTPS connections to the registry fail, allowing downgrade attacks.
While you can continue using Docker, failing to address CVE-2014-5277 increases the risk of data interception during image retrieval.