Docker before 1.3.3 does not properly validate image IDs, which allows remote attackers to conduct path traversal attacks and spoof repositories via a crafted image in a (1) "docker load" operation or (2) "registry communications."

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.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - Docker before 1.3.3 does not properly validate image IDs, which allows remote attackers to conduct path
    traversal attacks and spoof repositories via a crafted image in a (1) "docker load" operation or (2)
    "registry communications." (CVE-2014-9358)

This docker version upgrade fixes the following security and non security issues, and adds the also additional features :

  - Updated to 1.4.1 (2014-12-15) :

  - Runtime :

  - Fix issue with volumes-from and bind mounts not being     honored after create (fixes bnc#913213)

  - Added e2fsprogs as runtime dependency, this is required     when the devicemapper driver is used. (bnc#913211).

  - Fixed owner & group for docker.socket (thanks to Andrei     Dziahel and     https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752555     #5)

  - Updated to 1.4.0 (2014-12-11) :

  - Notable Features since 1.3.0 :

  - Set key=value labels to the daemon (displayed in `docker     info`), applied with new `-label` daemon flag

  - Add support for `ENV` in Dockerfile of the form: `ENV     name=value name2=value2...`

  - New Overlayfs Storage Driver

  - `docker info` now returns an `ID` and `Name` field

  - Filter events by event name, container, or image

  - `docker cp` now supports copying from container volumes

  - Fixed `docker tag`, so it honors `--force` when     overriding a tag for existing image.

  - Changes introduced by 1.3.3 (2014-12-11) :

  - Security :

  - Fix path traversal vulnerability in processing of     absolute symbolic links (CVE-2014-9356) - (bnc#909709)

  - Fix decompression of xz image archives, preventing     privilege escalation (CVE-2014-9357) - (bnc#909710)

  - Validate image IDs (CVE-2014-9358) - (bnc#909712)

  - Runtime :

  - Fix an issue when image archives are being read slowly

  - Client :

  - Fix a regression related to stdin redirection

  - Fix a regression with `docker cp` when destination is     the current directory

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

run tests inside a docker repo allow unitfile to use /etc/sysconfig/docker-network Security fix for CVE-2014-9357, CVE-2014-9358, CVE-2014-9356

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.

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

    [1.3.3-1.0.1]
    - Rename requirement of docker-io-pkg-devel in %package devel as docker-pkg-devel
    - Restore SysV init scripts for Oracle Linux 6
    - Require Oracle Unbreakable Enterprise Kernel Release 3 or higher
    - Rename as docker.
    - Re-enable btrfs graphdriver support

    [1.3.3-1]
    - Update source to 1.3.3 from https://github.com/docker/docker/releases/tag/v1.3.3       Path traversal during processing of absolute symlinks (CVE-2014-9356)       Escalation of privileges during decompression of LZMA (.xz) archives (CVE-2014-9357)

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.

This docker version update fixes the following security and non security issues and adds additional features.

  - Updated to 1.4.0 (2014-12-11) :

  - Notable Features since 1.3.0 :

  - Set key=value labels to the daemon (displayed in `docker     info`), applied with new `-label` daemon flag

  - Add support for `ENV` in Dockerfile of the form: `ENV     name=value name2=value2...`

  - New Overlayfs Storage Driver

  - `docker info` now returns an `ID` and `Name` field

  - Filter events by event name, container, or image

  - `docker cp` now supports copying from container volumes

  - Fixed `docker tag`, so it honors `--force` when     overriding a tag for existing image.

  - Changes introduced by 1.3.3 (2014-12-11) :

  - Security :

  - Fix path traversal vulnerability in processing of     absolute symbolic links (CVE-2014-9356) - (bnc#909709)

  - Fix decompression of xz image archives, preventing     privilege escalation (CVE-2014-9357) - (bnc#909710)

  - Validate image IDs (CVE-2014-9358) - (bnc#909712)

  - Runtime :

  - Fix an issue when image archives are being read slowly

  - Client :

  - Fix a regression related to stdin redirection

  - Fix a regression with `docker cp` when destination is     the current directory

Security fix for CVE-2014-9357, CVE-2014-9358, CVE-2014-9356 Revert to using upstream v1.3.2 release Resolves: rhbz#1169035, rhbz#1169151

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.

Path traversal attacks are possible in the processing of absolute symlinks. In checking symlinks for traversals, only relative links were considered. This allowed path traversals to exist where they should have otherwise been prevented. This was exploitable via both archive extraction and through volume mounts. This vulnerability allowed malicious images or builds from malicious Dockerfiles to write files to the host system and escape containerization, leading to privilege escalation. (CVE-2014-9356)

It has been discovered that the introduction of chroot for archive extraction in Docker 1.3.2 had introduced a privilege escalation vulnerability. Malicious images or builds from malicious Dockerfiles could escalate privileges and execute arbitrary code as a root user on the Docker host by providing a malicious 'xz' binary. (CVE-2014-9357)

It has been discovered that Docker does not sufficiently validate Image IDs as provided either via 'docker load' or through registry communications. This allows for path traversal attacks, causing graph corruption and manipulation by malicious images, as well as repository spoofing attacks. (CVE-2014-9358)

ID	Name	Product	Family	Severity
270307	SUSE SLES15: docker-stable / docker-stable-bash-completion / etc (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
418215	SCA: security update for github.com/docker/docker (GHSA-qmmc-jppf-32wv)	Tenable Cloud Security	SCA Checks	medium
418215	SCA: security update for github.com/docker/docker (GHSA-qmmc-jppf-32wv)	Tenable Self-Hosted Container Security	SCA Checks	medium
83667	SUSE SLES12 Security Update : docker (SUSE-SU-2015:0082-1)	Nessus	SuSE Local Security Checks	high
80981	Fedora 20 : docker-io-1.4.1-6.fc20 (2015-1128)	Nessus	Fedora Local Security Checks	critical
80329	Oracle Linux 6 / 7 : docker (ELSA-2014-3110)	Nessus	Oracle Linux Local Security Checks	high
80278	openSUSE Security Update : docker (openSUSE-SU-2014:1722-1)	Nessus	SuSE Local Security Checks	high
79954	Fedora 21 : docker-io-1.4.0-1.fc21 (2014-16839)	Nessus	Fedora Local Security Checks	critical
79875	Amazon Linux AMI : docker (ALAS-2014-461)	Nessus	Amazon Linux Local Security Checks	high

Detections

Analytics

CVE-2014-9358

medium

Tenable Plugins

critical

critical

medium

medium

high

critical

high

high

critical

high