Strix
26.1K

CVE-2016-4989

UnknownEPSS 0.46%

Last modified

CVE-2016-4989 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.46% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
0.46%

36.3th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
Setroubleshoot ProjectSetroubleshoot<= -
RedhatEnterprise Linux Desktop7.0
RedhatEnterprise Linux Hpc Node7.0
RedhatEnterprise Linux Server7.0
RedhatEnterprise Linux Workstation7.0

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-4989?
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.
How severe is CVE-2016-4989?
Severity scoring for CVE-2016-4989 is pending analysis. The EPSS model estimates a 0.46% probability of exploitation in the next 30 days.
How do I fix CVE-2016-4989?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2016

View all 2016CVEs →

Are you affected by CVE-2016-4989?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST