CVE-2015-3627 Symlink Attack in Libcontainer and Docker Engine

High 7.2 Published Updated

Local attackers can gain privileges via symlink attacks in Docker images due to improper file descriptor handling before chroot.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2015-3627?

CVE-2015-3627 is a high-severity path traversal vulnerability in n/a, published on 18 May 2015. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

Libcontainer and Docker Engine before 1.6.1 opens the file-descriptor passed to the pid-1 process before performing the chroot, which allows local users to gain privileges via a symlink attack in an image.

Weakness: CWE-59

Which versions are affected by CVE-2015-3627?

3 open source packages ship an affected version, including github.com/docker/docker. It affects 2 products.

PackageAffectedFixed in
github.com/docker/docker GoAll versions1.6.1
github.com/docker/docker GoAll versions1.6.1
github.com/docker/docker GoAll versions1.6.1

Products include Docker Docker, Docker Libcontainer.

How do I fix CVE-2015-3627?

Upgrade github.com/docker/docker to 1.6.1 or later.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2015-3627 being exploited?

There is no known exploitation of CVE-2015-3627 in the wild and no public exploit code.

Sources

Also known as DEBIAN-CVE-2015-3627, GHSA-g7v2-2qxx-wjrw, GO-2022-0649, UBUNTU-CVE-2015-3627.

Is CVE-2015-3627 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free