CVE-2014-0047: High severity Docker docker vulnerability
Docker before 1.5 allows local users to have unspecified impact via vectors involving unsafe /tmp usage.
Other sources
Kurt Seifried of the Red Hat Security Response Team reports:
A number of unsafe uses of /tmp, ranging from actual code to test code and documentation exmaples. In general many are due to unsafe use in bash scripts, and can be fixed by using mktemp() correctly. There is also at least one Ruby one (the Vagrant file) and several go scripts that use bash command lines unsafely.
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2014-0047?
CVE-2014-0047 has a medium severity rating due to potential vulnerabilities caused by unsafe usage of the /tmp directory.
How do I fix CVE-2014-0047?
To fix CVE-2014-0047, upgrade Docker to version 1.5 or later.
Who is affected by CVE-2014-0047?
Local users on systems running Docker versions prior to 1.5 are affected by CVE-2014-0047.
What are the implications of CVE-2014-0047?
The implications of CVE-2014-0047 include unauthorized access and potential code execution due to insecure handling of temporary files.
When was CVE-2014-0047 reported?
CVE-2014-0047 was reported in early 2014, highlighting security issues in Docker versions before 1.5.