The Oracle SQL92_SECURITY parameter must be set to TRUE.

From Oracle Database 12c Security Technical Implementation Guide

Part of SRG-APP-000516-DB-999900

Associated with: CCI-000366

SV-75919r1_rule The Oracle SQL92_SECURITY parameter must be set to TRUE.

Vulnerability discussion

The configuration option SQL92_SECURITY specifies whether table-level SELECT privileges are required to execute an update or delete that references table column values. If this option is disabled (set to FALSE), the UPDATE privilege can be used to determine values that should require SELECT privileges.The SQL92_SECURITY setting of TRUE prevents the exploitation of user credentials with only DELETE or UPDATE privileges on a table from being able to derive column values in that table by performing a series of update/delete statements using a where clause, and rolling back the change. In the following example, with SQL92_SECURITY set to FALSE, a user with only delete privilege on the scott.emp table is able to derive that there is one employee with a salary greater than 3000. With SQL92_SECURITY set to TRUE, that user is prevented from attempting to derive a value.SQL92_SECURITY = FALSESQL> delete from scott.emp where sal > 3000;1 row deletedSQL> rollback;Rollback completeSQL92_SECURITY = TRUESQL> delete from scott.emp where sal > 3000;delete from scott.emp where sal > 3000 *ERROR at line 1:ORA-01031: insufficient privileges

Check content

From SQL*Plus: select value from v$parameter where name = 'sql92_security'; If the value returned is set to FALSE, this is a finding. If the parameter is set to TRUE or does not exist, this is not a finding.

Fix text

Enable SQL92 security. From SQL*Plus: alter system set sql92_security = TRUE scope = spfile; The above SQL*Plus command will set the parameter to take effect at next system startup.

Pro Tips

Powered by sagemincer