Title

MarkLogic Server objects (including but not limited to indexes, storage, functions, triggers, links to software external to the server, etc.) must be owned by database/MarkLogic Server principals authorized for ownership. (Cat II impact)

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. Database functions and procedures can be coded using definer's rights. This allows anyone who utilizes the object to perform the actions if they were the owner. If not properly managed, this can lead to privileged actions being taken by unauthorized individuals. Conversely, if critical tables or other objects rely on unauthorized owner accounts, these objects may be lost when an account is removed.

Check Content

Review system documentation to identify accounts authorized to own database objects. Review accounts that own objects in the database(s). Perform the check from the MarkLogic Server Admin Interface with a user that holds administrative-level privileges. 1. Click the Security icon. 2. Click the Users icon on the left tree menu. 3. Inspect the Users. If there is a User who is not authorized to own database objects, this is a finding.

Fix Text

Assign ownership of authorized objects to authorized object owner accounts. Perform the fix from the MarkLogic Server Admin Interface with a user that holds administrative-level privileges. 1. Click the Security icon. 2. Click the Users icon on the left tree menu. 3. Inspect the Users. For users who are not authorized to own database objects, remove the users.

Additional Identifiers

Rule ID: SV-220358r879586_rule

Vulnerability ID: V-220358

Group Title: SRG-APP-000133-DB-000200

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.