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.

The remote SUSE Linux SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:03545-1 advisory.

    Note this update contains a already fixed references mostly.

    - Remove git-core recommends on SLE to avoid pulling it in unnecessary. (bsc#1250508)

      This feature is mostly intended for developers ('docker build git://') so       most users already have the dependency installed, and the error when git is       missing is fairly straightforward (so they can easily figure out what they       need to install).

    - Include historical changelog data from before the docker-stable fork. The       initial changelog entry did technically provide all the necessary       information, but our CVE tracking tools do not understand how the package is       forked and so it seems that this package does not include fixes for ~12 years       of updates. So, include a copy of the original package's changelog up until       the fork point. bsc#1250596

    - Update to docker-buildx v0.25.0. Upstream changelog:
      <https://github.com/docker/buildx/releases/tag/v0.25.0>

    - Update to Go 1.23 for building now that upstream has switched their 23.0.x       LTSS to use Go 1.23.

    - Do not try to inject SUSEConnect secrets when in Rootless Docker mode, as       Docker does not have permission to access the host zypper credentials in this       mode (and unprivileged users cannot disable the feature using       /etc/docker/suse-secrets-enable.) bsc#1240150

    - Initial docker-stable fork, forked from Docker 24.0.7-ce release       (packaged on 2024-02-14). The original changelog is included below for       historical reference.

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:03540-1 advisory.

    - Include historical changelog data from before the docker-stable fork. The       initial changelog entry did technically provide all the necessary       information, but our CVE tracking tools do not understand how the package is       forked and so it seems that this package does not include fixes for ~12 years       of updates. So, include a copy of the original package's changelog up until       the fork point. (bsc#1250596)

    - Remove git-core recommends on SLE. Most SLE systems have       installRecommends=yes by default and thus end up installing git with Docker.
      bsc#1250508

      This feature is mostly intended for developers ('docker build git://') so       most users already have the dependency installed, and the error when git is       missing is fairly straightforward (so they can easily figure out what they       need to install).

    - Backport <https://github.com/moby/moby/pull/48517>. bsc#1247362

    - Update to docker-buildx v0.25.0. Upstream changelog:
      <https://github.com/docker/buildx/releases/tag/v0.25.0>

    - Do not try to inject SUSEConnect secrets when in Rootless Docker mode, as       Docker does not have permission to access the host zypper credentials in this       mode (and unprivileged users cannot disable the feature using       /etc/docker/suse-secrets-enable.) bsc#1240150

    - Initial docker-stable fork, forked from Docker 24.0.7-ce release       (packaged on 2024-02-14). The original changelog is included below for       historical reference.

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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.
    (CVE-2014-5277)

Note that Nessus relies on the presence of the package as reported by the vendor.

Docker was updated to version 1.3.1 to fix two security issues and several other bugs.

These security issues were fixed :

  - Prevent fallback to SSL protocols lower than TLS 1.0 for     client, daemon and registry (CVE-2014-5277).

  - Secure HTTPS connection to registries with certificate     verification and without HTTP fallback unless     `--insecure-registry` is specified.

These non-security issues were fixed :

  - Fix issue where volumes would not be shared

  - Fix issue with `--iptables=false` not automatically     setting `--ip-masq=false`

  - Fix docker run output to non-TTY stdout

  - Fix escaping `$` for environment variables

  - Fix issue with lowercase `onbuild` Dockerfile     instruction

  - Restrict envrionment variable expansion to `ENV`, `ADD`,     `COPY`, `WORKDIR`, `EXPOSE`, `VOLUME` and `USER`

  - docker `exec` allows you to run additional processes     inside existing containers

  - docker `create` gives you the ability to create a     container via the cli without executing a process

  - `--security-opts` options to allow user to customize     container labels and apparmor profiles

  - docker `ps` filters

  - Wildcard support to copy/add

  - Move production urls to get.docker.com from     get.docker.io

  - Allocate ip address on the bridge inside a valid cidr

  - Use drone.io for pr and ci testing

  - Ability to setup an official registry mirror

  - Ability to save multiple images with docker `save`

go was updated to version 1.3.3 to fix one security issue and several other bugs.

This security issue was fixed :

  - TLS client authentication issue (CVE-2014-7189). These     non-security issues were fixed :

  - Avoid stripping debuginfo on arm, it fails (and is not     necessary)

  - Revert the /usr/share/go/contrib symlink as it caused     problems during update. Moved all go sources to     /usr/share/go/contrib/src instead of     /usr/share/go/contrib/src/pkg and created pkg and src     symlinks in contrib to add it to GOPATH

  - Fixed %go_contribsrcdir value

  - Copy temporary macros.go as go.macros to avoid it to be     built

  - Do not modify Source: files, because that makes the     .src.rpm being tied to one specific arch.

  - Removed extra src folder in /usr/share/go/contrib: the     goal is to transform this folder into a proper entry for     GOPATH. This folder is now linked to     %(_libdir)/go/contrib

  - go requires gcc to build sources using cgo

  - tools-packaging.patch: Allow building cover and vet     tools in $GOROOT_TARGET/pkg/tool instead of     $GOROOT/pkg/tool. This will allow building go tools as a     separate package

ID	Name	Product	Family	Severity
270307	SUSE SLES15 / openSUSE 15 Security Update : docker-stable (SUSE-SU-2025:03545-1)	Nessus	SuSE Local Security Checks	critical
270099	SUSE SLES12 Security Update : docker-stable (SUSE-SU-2025:03540-1)	Nessus	SuSE Local Security Checks	critical
218240	Linux Distros Unpatched Vulnerability : CVE-2014-5277	Nessus	Misc.	critical
79241	openSUSE Security Update : docker / go (openSUSE-SU-2014:1411-1)	Nessus	SuSE Local Security Checks	medium

Detections

Analytics

CVE-2014-5277

medium

Tenable Plugins

critical

critical

critical

medium