First published: Fri Jun 24 2011(Updated: )
It was found that systemtap runtime tool (staprun) did not properly enforce the module's path sanity check, when the ad-hoc module instrumentation via user-space probing with user-specified module path was requested. A local user, member of the 'stapusr' group could use this flaw to escalate their privileges.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Systemtap Systemtap | =1.1 | |
Systemtap Systemtap | =1.2 | |
Systemtap Systemtap | =0.3 | |
Systemtap Systemtap | =0.9.5 | |
Systemtap Systemtap | =0.4 | |
Systemtap Systemtap | =0.6.2 | |
Systemtap Systemtap | =0.5.10 | |
Systemtap Systemtap | =0.8 | |
Systemtap Systemtap | =0.9 | |
Systemtap Systemtap | =0.5.14 | |
Systemtap Systemtap | =0.7.2 | |
Systemtap Systemtap | =0.9.8 | |
Systemtap Systemtap | =0.7 | |
Systemtap Systemtap | =0.5.12 | |
Systemtap Systemtap | <=1.5 | |
Systemtap Systemtap | =0.5.4 | |
Systemtap Systemtap | =0.6 | |
Systemtap Systemtap | =0.5.7 | |
Systemtap Systemtap | =0.9.7 | |
Systemtap Systemtap | =1.4 | |
Systemtap Systemtap | =0.9.9 | |
Systemtap Systemtap | =0.5.8 | |
Systemtap Systemtap | =0.5.3 | |
Systemtap Systemtap | =0.2.2 | |
Systemtap Systemtap | =0.5.5 | |
Systemtap Systemtap | =0.5.13 | |
Systemtap Systemtap | =0.5.9 | |
Systemtap Systemtap | =1.0 | |
Systemtap Systemtap | =1.3 | |
Systemtap Systemtap | =0.5 | |
redhat/systemtap | <1.6 | 1.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.