Vulnerabilities · 2014 · Docker
CVE-2014-5277
Docker vulnerability
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.
Affected products
Docker, Docker-py. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Docker runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- lists.opensuse.org/opensuse-updates/2014-11/msg00048.html
- groups.google.com/forum/#%21topic/docker-user/oYm0i3xShJU
- nvd.nist.gov/vuln/detail/CVE-2014-5277
- github.com/docker/docker/commit/8caacb18f8019dfda30d79c327397e5f5783c068
- groups.google.com/forum/#!topic/docker-user/oYm0i3xShJU
- web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-5277
- github.com/advisories/GHSA-8w94-cf6g-c8mg
- nvd.nist.gov/vuln/detail/CVE-2014-5277
- cve.org/CVERecord?id=CVE-2014-5277
More vulnerabilities in Docker products
CVE-2026-6406CVE-2026-5843CVE-2026-5817CVE-2025-13743CVE-2025-3224CVE-2024-8696CVE-2024-8695CVE-2024-6222All 89
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.