Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1187340 - (CVE-2014-8163) CVE-2014-8163 Satellite5: upload_crash_file and upload_result directory traversal
CVE-2014-8163 Satellite5: upload_crash_file and upload_result directory trave...
Status: NEW
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=20150303,repor...
: Security
Depends On:
Blocks: 1181470 1187346
  Show dependency treegraph
 
Reported: 2015-01-29 14:34 EST by Kurt Seifried
Modified: 2015-09-10 19:16 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
It was found that an XMLRPC interface exposed by Satellite could allow an attacker to write arbitrary files and directories under the /var/satellite directory on the Satellite server.
Story Points: ---
Clone Of:
Environment:
Last Closed:
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 2015-01-29 14:34:22 EST
Travis Emmert reports:

An XMLRPC interface is exposed that is intended for programmatic invocation 
from the client programs and related components. This interfaces exists on the 
satellite server at /XMLRPC. Note that this interface is different from the 
published interface exposed to end­users at /rpc/api. The application accepts 
data and a filename for writing the file too. The filename and resulting 
generated path is inspected, however the inspection does not consider all 
potential attacks. The verification on the path results in a situation where 
an attacker can write to an arbitrary file and directory under /var/satellite/
Comment 2 Kurt Seifried 2015-05-11 12:13:13 EDT
Acknowledgement:

Red Hat would like to thank Travis Emmert for reporting this issue.

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