Docker 1.3.0 through 1.3.1 allows remote attackers to modify the default run profile of image containers and possibly bypass the container by applying unspecified security options to an image.

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.

docker was updated to version 1.3.2 to fix two security issues.

These security issues were fixed :

  - Symbolic and hardlink issues leading to privilege     escalation (CVE-2014-6407).

  - Potential container escalation (CVE-2014-6408).

There non-security issues were fixed :

  - Fix deadlock in docker ps -f exited=1

  - Fix a bug when --volumes-from references a container     that failed to start

  - --insecure-registry now accepts CIDR notation such as     10.1.0.0/16

  - Private registries whose IPs fall in the 127.0.0.0/8     range do no need the --insecure-registry flag

  - Skip the experimental registry v2 API when mirroring is     enabled

  - Fixed minor packaging issues.

The remote Oracle Linux 6 / 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2014-3095 advisory.

    - Update source to 1.3.2 from https://github.com/docker/docker/releases/tag/v1.3.2       Prevent host privilege escalation from an image extraction vulnerability (CVE-2014-6407).
      Prevent container escalation from malicious security options applied to images (CVE-2014-6408).
      The '--insecure-registry' flag of the 'docker run' command has undergone several refinements and     additions.
      You can now specify a sub-net in order to set a range of registries which the Docker daemon will     consider insecure.
      By default, Docker now defines 'localhost' as an insecure registry.
      Registries can now be referenced using the Classless Inter-Domain Routing (CIDR) format.
      When mirroring is enabled, the experimental registry v2 API is skipped.

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

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

Security fix for CVE-2014-6407, CVE-2014-6408

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Docker versions 1.3.0 through 1.3.1 allowed security options to be applied to images, allowing images to modify the default run profile of containers executing these images. This vulnerability could allow a malicious image creator to loosen the restrictions applied to a container's processes, potentially facilitating a break-out.
(CVE-2014-6408)

The Docker engine, up to and including version 1.3.1, was vulnerable to extracting files to arbitrary paths on the host during 'docker pull' and 'docker load' operations. This was caused by symlink and hardlink traversals present in Docker's image extraction. This vulnerability could be leveraged to perform remote code execution and privilege escalation. (CVE-2014-6407)

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
79819	openSUSE Security Update : docker (openSUSE-SU-2014:1596-1)	Nessus	SuSE Local Security Checks	high
79758	Oracle Linux 6 / 7 : docker (ELSA-2014-3095)	Nessus	Oracle Linux Local Security Checks	high
79704	Fedora 21 : docker-io-1.3.2-2.fc21 (2014-15779)	Nessus	Fedora Local Security Checks	high
79562	Amazon Linux AMI : docker (ALAS-2014-454)	Nessus	Amazon Linux Local Security Checks	high

Detections

Analytics

CVE-2014-6408

medium

Tenable Plugins

critical

critical

high

high

high

high