grsecurity RBAC improper privilege dropping
|grsecurity-rbac-admin-privileges (24156)||Medium Risk|
grsecurity, when configured to use RBAC (Role-Based Access Control) could allow a local attacker to gain elevated privileges. When RBAC is being used, if a user starts a service from an admin role and then logs out without using the gradm -u command, the affected service would retain admin role privileges. A local attacker could exploit this vulnerability to gain access to affected services with elevated privileges.
Upgrade to the latest version of grsecurity (2.1.8 or later), available from the grsecurity Web site. See References.
- grsecurity News Web site: [01/15] Important update for RBAC users: grsecurity 2.1.8 released for 2.4.32/220.127.116.11.
- BID-16261: GRSecurity Elevated Service Privileges Weakness
- CVE-2006-0228: The RBAC functionality in grsecurity before 2.1.8 does not properly handle when the admin role creates a service and then exits the shell without unauthenticating, which causes the service to be restarted with the admin role still active.
- OSVDB ID: 22464: grsecurity gradm RBAC Admin Role Unauthentication Security Issue
- SA18458: grsecurity RBAC Admin Role Dropping Security Issue
- VUPEN/ADV-2006-0199: grsecurity RBAC Admin Role Privileges Dropping Local Security Weakness
- grsecurity grsecurity 2.1.7 and prior
Jan 16, 2006
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email ignore thisxforceignore this@ignore thisus.ignore thisibm.comignore this