TMA-DB2-6.1.17
Secure SETSESSIONUSER Privilege
Description
The SETSESSIONUSER privilege allows one user to switch the session authorization ID of the connection to another user. This allows one user to run SQL statements as another user. It is recommended that Trusted Context be used as a stronger assertion of user identity where such a feature is required.
How it is checked
Audit method: Manual review
This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.
1. Connect to the Db2 database. db2 => connect to <dbname> 2. Run the following command: db2 => select distinct trustedid, trustedidtype, surrogateauthid, surrogateauthidtype from syscat.surrogateauthids where trustedidtype != 'C' 3. Review the list of users, groups, and roles in the above output to ensure only approved users, groups, and roles are assigned.
How it is fixed
Fix method: Guidance or infrastructure patch
Revoke this permission from any unauthorized users. 1. Connect to the Db2 database. db2 => connect to <dbname> 2. Run the following command: db2 => REVOKE SETSESSIONUSER ON <authid> FROM <authid>
Properties
- Operating systems
- Any
- Tags
- db2databasemanual
- Reference
- CIS IBM Db2 12.1 Benchmark v1.0.0 - 6.1.17 Secure SETSESSIONUSER Privilege