Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

oracle-oval логотип

ELSA-2020-5966

Опубликовано: 05 дек. 2020
Источник: oracle-oval
Платформа: Oracle Linux 7

Описание

ELSA-2020-5966: docker-cli docker-engine security update (IMPORTANT)

docker-cli [19.03.11-7]

  • Fix for CVE-2020-15257

[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

docker-engine [19.03.11-7]

  • Fix for CVE-2020-15257

[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]

Обновленные пакеты

Oracle Linux 7

Oracle Linux aarch64

docker-cli

19.03.11.ol-7.el7

docker-engine

19.03.11.ol-7.el7

Oracle Linux x86_64

docker-cli

19.03.11.ol-7.el7

docker-engine

19.03.11.ol-7.el7

Связанные CVE

Связанные уязвимости

CVSS3: 5.2
ubuntu
около 5 лет назад

containerd is an industry-standard container runtime and is available as a daemon for Linux and Windows. In containerd before versions 1.3.9 and 1.4.3, the containerd-shim API is improperly exposed to host network containers. Access controls for the shim’s API socket verified that the connecting process had an effective UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious containers running in the same network namespace as the shim, with an effective UID of 0 but otherwise reduced privileges, to cause new processes to be run with elevated privileges. This vulnerability has been fixed in containerd 1.3.9 and 1.4.3. Users should update to these versions as soon as they are released. It should be noted that containers started with an old version of containerd-shim should be stopped and restarted, as running containers will continue to be vulnerable even after an upgrade. If you are not providing the ability for untrusted users...

CVSS3: 8.8
redhat
около 5 лет назад

containerd is an industry-standard container runtime and is available as a daemon for Linux and Windows. In containerd before versions 1.3.9 and 1.4.3, the containerd-shim API is improperly exposed to host network containers. Access controls for the shim’s API socket verified that the connecting process had an effective UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious containers running in the same network namespace as the shim, with an effective UID of 0 but otherwise reduced privileges, to cause new processes to be run with elevated privileges. This vulnerability has been fixed in containerd 1.3.9 and 1.4.3. Users should update to these versions as soon as they are released. It should be noted that containers started with an old version of containerd-shim should be stopped and restarted, as running containers will continue to be vulnerable even after an upgrade. If you are not providing the ability for untrusted users...

CVSS3: 5.2
nvd
около 5 лет назад

containerd is an industry-standard container runtime and is available as a daemon for Linux and Windows. In containerd before versions 1.3.9 and 1.4.3, the containerd-shim API is improperly exposed to host network containers. Access controls for the shim’s API socket verified that the connecting process had an effective UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious containers running in the same network namespace as the shim, with an effective UID of 0 but otherwise reduced privileges, to cause new processes to be run with elevated privileges. This vulnerability has been fixed in containerd 1.3.9 and 1.4.3. Users should update to these versions as soon as they are released. It should be noted that containers started with an old version of containerd-shim should be stopped and restarted, as running containers will continue to be vulnerable even after an upgrade. If you are not providing the ability for untrusted users to

CVSS3: 5.2
debian
около 5 лет назад

containerd is an industry-standard container runtime and is available ...

suse-cvrf
около 5 лет назад

Security update for containerd, docker, docker-runc, golang-github-docker-libnetwork