Database objects must be owned by accounts authorized for ownership.

From Oracle Database 11.2g Security Technical Implementation Guide

Part of SRG-APP-000133-DB-000200

Associated with: CCI-001499

SV-66439r3_rule Database objects must be owned by accounts authorized for ownership.

Vulnerability discussion

Within the database, object ownership implies full privileges to the owned object including the privilege to assign access to the owned objects to other subjects. Unmanaged or uncontrolled ownership of objects can lead to unauthorized object grants and alterations, and unauthorized modifications to data. If critical tables or other objects rely on unauthorized owner accounts, these objects can be lost when an account is removed.It may be the case that there are accounts that are authorized to own synonyms, but no other objects. If this is so, it should be documented.

Check content

Review system documentation to identify accounts authorized to own database objects. Review accounts in DBMS that own objects. If any database objects are found to be owned by users not authorized to own database objects, this is a finding. Query the object DBA_OBJECTS to show the users who own objects in the database. The query below will return all of the users who own objects. sqlplus connect as sysdba SQL>select owner, object_type, count(*) from dba_objects group by owner, object_type order by owner, object_type; If these owners are not authorized owners, select all of the objects these owners have generated and decide who they should belong to. To make a list of all of the objects, the unauthorized owner has to perform the following query. SQL>select * from dba_objects where owner =&unauthorized_owner;

Fix text

Update system documentation to include list of accounts authorized for object ownership. Re-assign ownership of authorized objects to authorized object owner accounts.

Pro Tips

Powered by sagemincer