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 1339183 - (CVE-2016-4445) CVE-2016-4445 setroubleshoot: insecure use of commands.getstatusoutput in sealert
CVE-2016-4445 setroubleshoot: insecure use of commands.getstatusoutput in sea...
Status: CLOSED ERRATA
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=20160621,repor...
: Security
Depends On: 1339375 1339377
Blocks: 1332645
  Show dependency treegraph
 
Reported: 2016-05-24 06:49 EDT by Tomas Hoger
Modified: 2016-11-08 10:56 EST (History)
7 users (show)

See Also:
Fixed In Version: setroubleshoot 3.2.23
Doc Type: Bug Fix
Doc Text:
A shell command injection flaw was found in the way the setroubleshoot executed external commands. A local attacker able to trigger certain SELinux denials could use this flaw to execute arbitrary code with root privileges.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-06-22 05:09:48 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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1267 normal SHIPPED_LIVE Important: setroubleshoot and setroubleshoot-plugins security update 2016-06-21 21:24:18 EDT

  None (edit)
Description Tomas Hoger 2016-05-24 06:49:55 EDT
It was discovered that sealert executed external fix commands using commands.getstatusoutput() without properly sanitizing untrusted inputs used as command arguments.  These inputs originated from SELinux AVC messages.  A local user could use this flaw to execute arbitrary code as root if they could trigger an SELinux denial using a file with a specially crafted name.

The use of commands.getstatusoutput() was already removed upstream via the following commit:

https://github.com/fedora-selinux/setroubleshoot/commit/2d12677629ca319310f6263688bb1b7f676c01b7
Comment 1 Tomas Hoger 2016-05-24 06:53:36 EDT
Acknowledgments:

Name: Red Hat Product Security
Comment 8 Tomas Hoger 2016-06-21 07:36:48 EDT
Lifting embargo.
Comment 9 errata-xmlrpc 2016-06-21 17:24:56 EDT
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6

Via RHSA-2016:1267 https://access.redhat.com/errata/RHSA-2016:1267
Comment 10 Tomas Hoger 2016-06-22 05:04:59 EDT
This issue was fixed upstream in version 3.2.23.  The setroubleshoot packages in Red Hat Enterprise Linux 7 were updated from version 3.2.17 to version 3.2.24 via RHBA-2015:2287, released as part of Red Hat Enterprise Linux 7.2.

https://rhn.redhat.com/errata/RHBA-2015-2287.html

Therefore, this issue was corrected in that update.

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