CVE-2014-0047
First published: Tue Feb 11 2014(Updated: )
Docker before 1.5 allows local users to have unspecified impact via vectors involving unsafe /tmp usage.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Python Docker | <=1.4.1 |
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.
Reference Links
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.
- agent/type
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/last-modified-date
- agent/references
- agent/severity
- agent/description
- agent/event
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2014-0047
- agent/trending
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/docker
- canonical/python docker
- version/python docker/1.4.1