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
Created trafficserver tracking bugs for this issue: Affects: fedora-all [bug 1103173] Affects: epel-6 [bug 1103174]
Will doing PrivateTmp=true be an acceptable workaround for fedora-all ?
(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
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.