CVE-2015-3627: High severity Docker docker vulnerability
Published May 18, 2015
·Updated
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.
Affected Software
2 affected components
Docker docker<=1.6
Docker Libcontainer Docker<=1.6.0
Event History
May 18, 2015
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2015-3627?
CVE-2015-3627 is considered a high severity vulnerability due to its potential for privilege escalation.
2
How do I fix CVE-2015-3627?
To fix CVE-2015-3627, update Docker and Libcontainer to version 1.6.1 or later.
3
What types of systems are affected by CVE-2015-3627?
CVE-2015-3627 affects Docker Engine and Libcontainer versions prior to 1.6.1.
4
Can local users exploit CVE-2015-3627?
Yes, local users can exploit CVE-2015-3627 through a symlink attack to gain elevated privileges.
5
What is the impact of CVE-2015-3627 on Docker?
The impact of CVE-2015-3627 on Docker can lead to unauthorized privilege escalation for local users.