CVE-2016-4989: setroubleshoot allows local users to bypass an intended container protection mechanism and execute arbitrary commands by (1) triggering an…
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.45% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: setroubleshoot (Red Hat:enterprise_linux:6::client) 0:3.0.47-12.el6_8; setroubleshoot-debuginfo (Red Hat:enterprise_linux:6::client) 0:3.0.47-12.el6_8; setroubleshoot-doc (Red Hat:enterprise_linux:6::client) 0:3.0.47-12.el6_8.
Low priority for now. Upgrade to setroubleshoot (Red Hat:enterprise_linux:6::client) 0:3.0.47-12.el6_8; setroubleshoot-debuginfo (Red Hat:enterprise_linux:6::client) 0:3.0.47-12.el6_8; setroubleshoot-doc (Red Hat:enterprise_linux:6::client) 0:3.0.47-12.el6_8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Apr 11, 2017
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 40th percentile
- CWE
- CWE-77
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| setroubleshoot project | setroubleshoot | cpe:2.3:a:setroubleshoot_project:setroubleshoot |
| redhat | enterprise linux desktop | cpe:2.3:o:redhat:enterprise_linux_desktop |
| redhat | enterprise linux hpc node | cpe:2.3:o:redhat:enterprise_linux_hpc_node |
| redhat | enterprise linux server | cpe:2.3:o:redhat:enterprise_linux_server |
| redhat | enterprise linux workstation | cpe:2.3:o:redhat:enterprise_linux_workstation |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat enterprise linux desktop7.0
- redhat enterprise linux hpc node7.0
- redhat enterprise linux server7.0
- redhat enterprise linux workstation7.0
- setroubleshoot project setroubleshootup to - inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:enterprise_linux:6::client | setroubleshoot | before 0:3.0.47-12.el6_8 | 0:3.0.47-12.el6_8 |
| Red Hat:enterprise_linux:6::client | setroubleshoot-debuginfo | before 0:3.0.47-12.el6_8 | 0:3.0.47-12.el6_8 |
| Red Hat:enterprise_linux:6::client | setroubleshoot-doc | before 0:3.0.47-12.el6_8 | 0:3.0.47-12.el6_8 |
| Red Hat:enterprise_linux:6::client | setroubleshoot-plugins | before 0:3.0.40-3.1.el6_8 | 0:3.0.40-3.1.el6_8 |
| Red Hat:enterprise_linux:6::client | setroubleshoot-server | before 0:3.0.47-12.el6_8 | 0:3.0.47-12.el6_8 |
| Red Hat:enterprise_linux:7::client | setroubleshoot | before 0:3.2.24-4.el7_2 | 0:3.2.24-4.el7_2 |
| Red Hat:enterprise_linux:7::client | setroubleshoot-debuginfo | before 0:3.2.24-4.el7_2 | 0:3.2.24-4.el7_2 |
| Red Hat:enterprise_linux:7::client | setroubleshoot-plugins | before 0:3.0.59-2.el7_2 | 0:3.0.59-2.el7_2 |
| Red Hat:enterprise_linux:7::client | setroubleshoot-server | before 0:3.2.24-4.el7_2 | 0:3.2.24-4.el7_2 |
Same product
setroubleshoot project: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-4446The allow_execstack plugin for setroubleshoot allows local users to execute arbitrary commands by triggering an execstack SELinux denial…28Monitor
- CVE-2016-4445The fix_lookup_id function in sealert in setroubleshoot before 3.2.23 allows local users to execute arbitrary commands as root by…28Monitor
- CVE-2016-4444The allow_execmod plugin for setroubleshoot before 3.2.23 allows local users to execute arbitrary commands by triggering an execmod SELinux…28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| red hat:setroubleshoot | 0:3.0.47-12.el6_8 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:setroubleshoot-debuginfo | 0:3.0.47-12.el6_8 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:setroubleshoot-doc | 0:3.0.47-12.el6_8 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:setroubleshoot-plugins | 0:3.0.40-3.1.el6_8 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:setroubleshoot-server | 0:3.0.47-12.el6_8 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')CVSS vector
CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- LDAP InjectionCAPEC-136likelihood: High · High
- Command DelimitersCAPEC-15likelihood: High · High
- IMAP/SMTP Command InjectionCAPEC-183Medium
- Command InjectionCAPEC-248likelihood: Medium · High
- Manipulating Writeable Terminal DevicesCAPEC-40likelihood: High · Very High
- Exploiting Multiple Input Interpretation LayersCAPEC-43likelihood: Medium · High
- Manipulating Writeable Configuration FilesCAPEC-75likelihood: High · Very High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- securitytracker.com/id/1036144
- access.redhat.com/errata/RHSA-2016:1293
- bugzilla.redhat.com/show_bug.cgi?id=1346461
- github.com/fedora-selinux/setroubleshoot/commit/dda55aa50db95a25f0d919c3a0d5871827cdc40f
- github.com/fedora-selinux/setroubleshoot/commit/e69378d7e82a503534d29c5939fa219341e8f2ad
- rhn.redhat.com/errata/RHSA-2016-1267.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.