Bug 1063549 - (CVE-2014-0047) CVE-2014-0047 Docker: multiple temporary file creation vulnerabilities
CVE-2014-0047 Docker: multiple temporary file creation vulnerabilities
Status: CLOSED CURRENTRELEASE
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20150324,repor...
: Security
Depends On: 1063553
Blocks: 1063551
  Show dependency treegraph
 
Reported: 2014-02-10 20:24 EST by Kurt Seifried
Modified: 2015-03-24 03:20 EDT (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-03-24 01:19:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Kurt Seifried 2014-02-10 20:24:50 EST
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.
Comment 2 Trevor Jay 2015-03-24 01:19:04 EDT
Under 1.5, I deleted /tmp, started the docker service, pulled an image, and started a container with no mishaps or creation of /tmp.

Note You need to log in before you can comment on or make changes to this bug.