PatchTheCVEsetroubleshoot project vulnerabilities
Recent CVEs affecting setroubleshoot project products. 4 tracked.
setroubleshoot project has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2017-04-11. Highest priority: CVE-2016-4446 (score 45/100).
- CVE-2016-4989 HIGH 7.0 UPGRADE MITIGATE setroubleshoot allows local users to bypass an intended container protection mechanism and execute arbitrary c
- CVE-2016-4446 HIGH 7.0 UPGRADE MITIGATE The allow_execstack plugin for setroubleshoot allows local users to execute arbitrary commands by triggering a
- CVE-2016-4445 HIGH 7.0 UPGRADE MITIGATE The fix_lookup_id function in sealert in setroubleshoot before 3.2.23 allows local users to execute arbitrary
- CVE-2016-4444 HIGH 7.0 UPGRADE MITIGATE The allow_execmod plugin for setroubleshoot before 3.2.23 allows local users to execute arbitrary commands by
FAQ
How do I fix setroubleshoot project vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is setroubleshoot project being exploited right now?
None of the tracked setroubleshoot project CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which setroubleshoot project CVE should I patch first?
CVE-2016-4446 currently ranks highest (45/100): The allow_execstack plugin for setroubleshoot allows local users to execute arbitrary commands by triggering a.