setroubleshoot allows local users to bypass an intended container protection mechanism and execute arbitrary commands by (1) triggering an SELinux denial with a crafted file name, which is handled by the _set_tpath function in audit_data.py or via a crafted (2) local_id or (3) analysis_id field in a crafted XML document to the run_fix function in SetroubleshootFixit.py, related to the subprocess.check_output and commands.getstatusoutput functions, a different vulnerability than CVE-2016-4445.
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
|Name||Vendor||Start Version||End Version|
|Red Hat Enterprise Linux 6||RedHat||setroubleshoot-0:3.0.47-12.el6_8||*|
|Red Hat Enterprise Linux 6||RedHat||setroubleshoot-plugins-0:3.0.40-3.1.el6_8||*|
|Red Hat Enterprise Linux 7||RedHat||setroubleshoot-0:3.2.24-4.el7_2||*|
|Red Hat Enterprise Linux 7||RedHat||setroubleshoot-plugins-0:3.0.59-2.el7_2||*|
Command injection vulnerabilities typically occur when:
Many protocols and products have their own custom command language. While OS or shell command strings are frequently discovered and targeted, developers may not realize that these other command languages might also be vulnerable to attacks. Command injection is a common problem with wrapper programs.