Описание
ELSA-2020-5900: docker-engine docker-cli security update (IMPORTANT)
docker-engine [19.03.11-6]
- Fix for CVE-2020-15157
[19.03.11-5]
- Bugfix for 'docker images [name]' not working on docker 19.03.11-ol
- Address CVE-2020-16845
[19.03.11-4]
- added patch for registry list
[19.03.11-3]
- update to 19.03.11 for CVE-2020-13401
[19.03.1-1.0.0]
- update to 19.03.1
[19.03-0.0.1]
- update to 19.03
[18.09.1-1.0.6]
- disable kmem accounting for UEKR4
[18.09.1-1.0.5]
- apply e4931e664feac6fa8846f3f04268a0cc98822549, fixes CVE-2019-5736
[18.09.1-1.0.4]
- fix authentication error when using docker hub and using --default-registry
[18.09.1-1.0.3]
- fix authentication errors when using docker hub
[18.09.1-1.0.2]
- use epoch in container-selinux dependency
[18.09.1-1.0.1]
- fix 'docker cp doesn't work for btrfs' (OLM-158)
- update build to Go 1.10.8
[18.09.1-1.0.0]
- update to 18.09.1
[18.09-1.0.0]
- rename back to docker-engine, rename dockerd-ce to dockerd and stop using alternatives
[18.09-0.0.1]
- merge docker-engine.spec changes by Oracle into docker-ce.spec from upstream 18.09 branch
[18.03.1.ol-0.0.7]
- fix [orabug 28452214] and [orabug 28461404]
[18.03.1.ol-0.0.6]
- obsolete/provide the docker package [orabug 28216396]
- Fix docker plugin reference resolution [orabug 28376247]
[18.03.1.ol-1.0.4]
- Fixed issue where RPM overwrites config files
[17.12.0.ol-1.0.1]
- Update docker-engine package for upstream 17.12.0
[17.09.1.ol-1.0.2]
- Update docker-engine package for upstream 17.09.1
[17.06.2.ol-1.0.1]
- Update docker-engine package for upstream 17.06.2 [orabug 26673768]
- Migrate to new 'ol'-based versioning
- add docker-storage-config utility
[17.03.1-ce-3.0.1]
- Update docker-engine package for upstream 17.03.1
- Enable configuration of Docker daemon via sysconfig [orabug 21804877]
- Require UEK4 for docker 1.9 [orabug 22235639 22235645]
- Add docker.conf for prelink [orabug 25147708]
- Update oracle linux selinux policy to match upstream [orabug 25653794]
- Use dockerd instead of docker daemon as it is deprecated [orabug 25653794]
docker-cli [19.03.11-6]
- Fix for CVE-2020-15157
[19.03.11-5]
- Bugfix for 'docker images [name]' not working on docker 19.03.11-ol
- Address CVE-2020-16845
[19.03.11-4]
- added patch for registry list
[19.03.11-3]
- update to 19.03.11 for CVE-2020-13401
[19.03.1-1.0.0]
- update to 19.03.1
[19.03-0.0.1]
- update to 19.03
[18.09.1-1.0.6]
- disable kmem accounting for UEKR4
[18.09.1-1.0.5]
- apply e4931e664feac6fa8846f3f04268a0cc98822549, fixes CVE-2019-5736
[18.09.1-1.0.4]
- fix authentication error when using docker hub and using --default-registry
[18.09.1-1.0.3]
- fix authentication errors when using docker hub
[18.09-1.0.0]
- rename to docker-cli
[18.09-0.0.1]
- merge docker-engine.spec changes by Oracle into docker-ce-cli.spec from upstream 18.09 branch
Обновленные пакеты
Oracle Linux 7
Oracle Linux aarch64
docker-cli
19.03.11.ol-6.el7
docker-engine
19.03.11.ol-6.el7
Oracle Linux x86_64
docker-cli
19.03.11.ol-6.el7
docker-engine
19.03.11.ol-6.el7
Связанные CVE
Связанные уязвимости
In containerd (an industry-standard container runtime) before version 1.2.14 there is a credential leaking vulnerability. If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format includes a URL for the location of a specific image layer (otherwise known as a “foreign layer”), the default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or later, the default containerd resolver will provide its authentication credentials if the server where the URL is located presents an HTTP 401 status code along with registry-specific HTTP headers. If an attacker publishes a public image with a manifest that directs one of the layers to be fetched from a web server they control and they trick a user or system into pulling the image, they can obtain the credentials used for pulling that image. In some cases, this may be the user's username and password for the registry. In other cases, this may be the credentials attached...
In containerd (an industry-standard container runtime) before version 1.2.14 there is a credential leaking vulnerability. If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format includes a URL for the location of a specific image layer (otherwise known as a “foreign layer”), the default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or later, the default containerd resolver will provide its authentication credentials if the server where the URL is located presents an HTTP 401 status code along with registry-specific HTTP headers. If an attacker publishes a public image with a manifest that directs one of the layers to be fetched from a web server they control and they trick a user or system into pulling the image, they can obtain the credentials used for pulling that image. In some cases, this may be the user's username and password for the registry. In other cases, this may be the credentials attached...
In containerd (an industry-standard container runtime) before version 1.2.14 there is a credential leaking vulnerability. If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format includes a URL for the location of a specific image layer (otherwise known as a “foreign layer”), the default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or later, the default containerd resolver will provide its authentication credentials if the server where the URL is located presents an HTTP 401 status code along with registry-specific HTTP headers. If an attacker publishes a public image with a manifest that directs one of the layers to be fetched from a web server they control and they trick a user or system into pulling the image, they can obtain the credentials used for pulling that image. In some cases, this may be the user's username and password for the registry. In other cases, this may be the credentials attached to
In containerd (an industry-standard container runtime) before version ...
containerd v1.2.x can be coerced into leaking credentials during image pull