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.

How do I fix CVE-2015-3629?

To mitigate CVE-2015-3629, upgrade the affected software to version 1.6.1 or higher.

Which versions of Docker are affected by CVE-2015-3629?

CVE-2015-3629 affects Docker Engine version 1.6.0.

What type of attack does CVE-2015-3629 address?

CVE-2015-3629 addresses a symlink attack that facilitates container escape.

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.

Vulnerability/
CVE-2015-3629

high

8.4

CWE

18/5/2015

15/2/2022

6/8/2024

CVE-2015-3629

First published: Mon 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.

Credit: cve@mitre.org cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
go/github.com/docker/docker	>=1.6.0<1.6.1	1.6.1
Docker Libcontainer	=1.6.0
openSUSE	=13.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

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.
How do I fix CVE-2015-3629?
To mitigate CVE-2015-3629, upgrade the affected software to version 1.6.1 or higher.
Which versions of Docker are affected by CVE-2015-3629?
CVE-2015-3629 affects Docker Engine version 1.6.0.
What type of attack does CVE-2015-3629 address?
CVE-2015-3629 addresses a symlink attack that facilitates container escape.
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.

agent/type
agent/weakness
agent/description
collector/github-advisory-latest
source/GitHub
alias/GHSA-g44j-7vp3-68cv
alias/CVE-2015-3629
agent/software-canonical-lookup
agent/severity
agent/references
agent/author
collector/github-advisory
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/trending
agent/source
agent/softwarecombine
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-cve
source/NVD
collector/nvd-api
package-manager/go
vendor/docker
canonical/docker libcontainer
version/docker libcontainer/1.6.0
vendor/opensuse
canonical/opensuse
version/opensuse/13.2

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

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.
How do I fix CVE-2015-3629?
To mitigate CVE-2015-3629, upgrade the affected software to version 1.6.1 or higher.
Which versions of Docker are affected by CVE-2015-3629?
CVE-2015-3629 affects Docker Engine version 1.6.0.
What type of attack does CVE-2015-3629 address?
CVE-2015-3629 addresses a symlink attack that facilitates container escape.
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.