high
7.5
CWE
362
Advisory Published
Updated

CVE-2018-15664: Race Condition

First published: Thu May 23 2019(Updated: )

In Docker through 18.06.1-ce-rc2, the API endpoints behind the 'docker cp' command are vulnerable to a symlink-exchange attack with Directory Traversal, giving attackers arbitrary read-write access to the host filesystem with root privileges, because daemon/archive.go does not do archive operations on a frozen filesystem (or from within a chroot).

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
debian/docker.io
20.10.5+dfsg1-1+deb11u2
20.10.5+dfsg1-1+deb11u3
20.10.24+dfsg1-1+deb12u1
26.1.5+dfsg1-4
Docker=17.06.0-ce
Docker=17.06.0-ce-rc1
Docker=17.06.0-ce-rc2
Docker=17.06.0-ce-rc3
Docker=17.06.0-ce-rc4
Docker=17.06.0-ce-rc5
Docker=17.06.1-ce
Docker=17.06.1-ce-rc1
Docker=17.06.1-ce-rc2
Docker=17.06.1-ce-rc3
Docker=17.06.1-ce-rc4
Docker=17.06.2-ce
Docker=17.06.2-ce-rc1
Docker=17.07.0-ce
Docker=17.07.0-ce-rc1
Docker=17.07.0-ce-rc2
Docker=17.07.0-ce-rc3
Docker=17.07.0-ce-rc4
Docker=17.09.0-ce
Docker=17.09.0-ce-rc1
Docker=17.09.0-ce-rc2
Docker=17.09.0-ce-rc3
Docker=17.09.1-ce
Docker=17.09.1-ce--rc1
Docker=17.10.0-ce
Docker=17.10.0-ce-rc1
Docker=17.10.0-ce-rc2
Docker=17.11.0-ce
Docker=17.11.0-ce-rc1
Docker=17.11.0-ce-rc2
Docker=17.11.0-ce-rc3
Docker=17.11.0-ce-rc4
Docker=17.12.0-ce
Docker=17.12.0-ce-rc1
Docker=17.12.0-ce-rc2
Docker=17.12.0-ce-rc3
Docker=17.12.0-ce-rc4
Docker=17.12.1-ce
Docker=17.12.1-ce-rc1
Docker=17.12.1-ce-rc2
Docker=18.01.0-ce
Docker=18.01.0-ce-rc1
Docker=18.02.0-ce
Docker=18.02.0-ce-rc1
Docker=18.02.0-ce-rc2
Docker=18.03.0-ce
Docker=18.03.0-ce-rc1
Docker=18.03.0-ce-rc2
Docker=18.03.0-ce-rc3
Docker=18.03.0-ce-rc4
Docker=18.03.1-ce
Docker=18.03.1-ce-rc1
Docker=18.03.1-ce-rc2
Docker=18.04.0-ce
Docker=18.04.0-ce-rc1
Docker=18.04.0-ce-rc2
Docker=18.05.0-ce
Docker=18.05.0-ce-rc1
Docker=18.06.0-ce
Docker=18.06.0-ce-rc1
Docker=18.06.0-ce-rc2
Docker=18.06.0-ce-rc3
Docker=18.06.1-ce-rc1
Docker=18.06.1-ce-rc2

Remedy

https://github.com/moby/moby/commit/d089b639372a8f9301747ea56eaf0a42df24016a

Remedy

https://github.com/moby/moby/commit/3029e765e241ea2b5249868705dbf9095bc4d529

Remedy

https://github.com/moby/moby/commit/fb5fe241b5931c7031fc4aa2ad4ca61159888df1

Remedy

https://github.com/moby/moby/pull/39292

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2018-15664?

    CVE-2018-15664 is considered critical as it allows arbitrary read-write access to the host filesystem with root privileges.

  • How do I fix CVE-2018-15664?

    To fix CVE-2018-15664, update Docker to versions 20.10.5+dfsg1-1+deb11u2 or later, or apply applicable patches.

  • Which Docker versions are affected by CVE-2018-15664?

    CVE-2018-15664 affects Docker versions prior to 20.10.5, including various releases from 17.06.0-ce up to 18.06.1-ce.

  • What type of attack does CVE-2018-15664 exploit?

    CVE-2018-15664 exploits a symlink-exchange vulnerability along with directory traversal attacks.

  • What are the consequences of exploiting CVE-2018-15664?

    Exploitation of CVE-2018-15664 can result in unauthorized access to sensitive files and potential system compromise due to root-level access.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203