Описание
Man-in-the-Middle (MitM)
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.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2014-5277
- https://github.com/docker/docker/commit/8caacb18f8019dfda30d79c327397e5f5783c068
- https://groups.google.com/forum/#!topic/docker-user/oYm0i3xShJU
- https://groups.google.com/forum/#%21topic/docker-user/oYm0i3xShJU
- https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-5277
- http://lists.opensuse.org/opensuse-updates/2014-11/msg00048.html
Пакеты
github.com/docker/docker
< 1.3.1
1.3.1
Связанные уязвимости
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.
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.
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.
Docker before 1.3.1 and docker-py before 0.5.3 fall back to HTTP when ...