Bug 1103172

Summary: trafficserver: insecure temporary file usage
Product: [Other] Security Response Reporter: Martin Prpič <mprpic>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED UPSTREAM QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: janfrode, jrusnack
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-08 02:33:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1103173, 1103174    
Bug Blocks:    

Description Martin Prpič 2014-05-30 12:19:27 UTC
It was found [1] that the Apache Traffic Server (trafficserver) creates temporary files in an insecure way. The original report [1] identifies the following problematic files:

    /bin/mv -f /tmp/shadow /etc/shadow
    /bin/sort /tmp/zonetab.tmp > /tmp/zonetab
    /bin/cp -f %s/net_config.xml /tmp/net_config.xml
    /tmp/dhcp_status
    /tmp/route_status
    /tmp/shadow

Though, grepping for "tmp/" in both trafficserver-3.2.5 and trafficserver-4.2.1 reveals a variety of other insecurely created temporary files.

A local attacker could use this flaw to perform a symbolic link attack.

Currently, no patch exists to resolve this issue.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749846

Comment 1 Martin Prpič 2014-05-30 12:21:01 UTC
Created trafficserver tracking bugs for this issue:

Affects: fedora-all [bug 1103173]
Affects: epel-6 [bug 1103174]

Comment 2 Jan-Frode Myklebust 2014-05-30 12:59:57 UTC
Will doing PrivateTmp=true be an acceptable workaround for fedora-all ?

Comment 3 Martin Prpič 2014-06-02 17:26:19 UTC
(In reply to Jan-Frode Myklebust from comment #2)
> Will doing PrivateTmp=true be an acceptable workaround for fedora-all ?

Hi Jan,

Sorry for the late reply. Using PrivateTmp is a sufficient workaround, although a real fix (using mktemp() to generate tmp files) for these issues would be preferable. It provides higher value to both upstream and downstream consumers and fixes these issues once and for all.

Also, note that this issue has been raised upstream:

https://issues.apache.org/jira/browse/TS-2867

Comment 4 Product Security DevOps Team 2019-06-08 02:33:14 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.