CVE-2014-6408: Access Restriction Bypass in Docker
Summary
CVE-2014-6408: Access Restriction Bypass in Docker. Affects github.com/docker/docker versions >= 1.3.0, < 1.3.2. Fixed in 1.3.2. How to fix ↓
Also tracked for
- docker.io · Debian:11
The same CVE-2014-6408 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Docker is a popular containerization platform written in Go. It allows users to package applications and their dependencies into lightweight, portable containers. Docker provides an efficient and scalable way to deploy and manage applications across different environments. However, versions 1.3.0 through 1.3.1 of Docker are vulnerable to an access restriction bypass.
Vulnerability Detail
The vulnerability in Docker 1.3.0 through 1.3.1 allows remote attackers to modify the default run profile of image containers and potentially bypass the container by applying unspecified security options to an image. This means that an attacker could gain unauthorized access to the container and perform malicious actions within the containerized environment. The exact details of the security options and their impact are not specified in the vulnerability report.
How To Fix
Latest published version: v28.5.2+incompatible as of 22 Oct 2026
go get github.com/docker/docker@v28.5.2+incompatibleUpgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
1.3.2
This is the first release that contains the fix.
go get github.com/docker/docker@v1.3.2Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
No specific workaround is mentioned in the vulnerability report. However, users can mitigate the risk by ensuring that their Docker images and containers are properly secured and that only trusted images are used. Additionally, it is important to regularly update Docker to the latest stable version to benefit from security fixes and improvements.
Conclusion
The access restriction bypass vulnerability in Docker versions 1.3.0 through 1.3.1 can potentially allow unauthorized access to containerized environments. It is crucial to upgrade Docker to version 1.3.2 or later to mitigate this vulnerability. Regularly updating Docker and following security best practices will help ensure a secure containerization environment. For further support on vulnerability remediation, contact DevNack.com.
See every vulnerability recorded for github.com/docker/docker →
FAQ
Docker is a containerization platform that allows users to package applications and their dependencies into lightweight, portable containers.
Versions 1.3.0 through 1.3.1 of Docker are affected by this vulnerability.
To fix this vulnerability, upgrade Docker to version 1.3.2 or later.
No specific workaround is mentioned in the vulnerability report. However, users can mitigate the risk by ensuring proper security measures and using trusted Docker images.
For more information about Docker security, refer to the official Docker documentation and security guidelines.
Related vulnerabilities
Recent vulnerabilities recorded for github.com/docker/docker.
