CVE-2015-3629: High severity docker libcontainer vulnerability
Published May 18, 2015
·Updated
Libcontainer 1.6.0, as used in Docker Engine, allows local users to escape containerization ("mount namespace breakout") and write to arbitrary file on the host system via a symlink attack in an image when respawning a container.
Affected Software
3 affected componentsFixes available
go/github.com/docker/docker>=1.6.0<1.6.1
1.6.1
Docker Libcontainer Docker=1.6.0
openSUSE openSUSE=13.2
Event History
May 18, 2015
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description
Feb 15, 2022
Advisory Published
via GitHub·01:57 AM
Frequently Asked Questions
1
What is the severity of CVE-2015-3629?
CVE-2015-3629 is considered to be high severity due to its potential for local privilege escalation and container escape.
2
How do I fix CVE-2015-3629?
To mitigate CVE-2015-3629, upgrade the affected software to version 1.6.1 or higher.
3
Which versions of Docker are affected by CVE-2015-3629?
CVE-2015-3629 affects Docker Engine version 1.6.0.
4
What type of attack does CVE-2015-3629 address?
CVE-2015-3629 addresses a symlink attack that facilitates container escape.
5
Who is impacted by CVE-2015-3629?
Local users on systems running Docker Engine version 1.6.0 are impacted by CVE-2015-3629, allowing them to write to arbitrary files on the host.