← Back to VMW vRealize Operations Manager 6.x PostgreSQL Security Technical Implementation Guide

V-239791

CAT II (Medium)

vROps PostgreSQL DB objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to the DBMS, etc.) must be owned by vROps PostgreSQL DB principals authorized for ownership.

Rule ID

SV-239791r879586_rule

STIG

VMW vRealize Operations Manager 6.x PostgreSQL Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-001499

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

At the command prompt, execute the following command:

# /opt/vmware/vpostgres/current/bin/psql -U postgres -c "\dp;"

Review the Access Privileges column. If any tables have permissions to users other than "postgres", this is a finding.

Fix Text

At the command prompt, execute the following command:

# /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER TABLE <tablename> OWNER TO postgres;"

Replace <tablename> with the name of the table discovered during the check.