Detections
Analytics

4.3 Ensure excessive function privileges are revoked

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

In certain situations, to provide required functionality, PostgreSQL needs to execute internal logic (stored procedures, functions, triggers, etc.) and/or external code modules with elevated privileges. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking the functionality applications/programs, those users are indirectly provided with greater privileges than assigned by their organization. This is known as privilege elevation. Privilege elevation must be utilized only where necessary. Execute privileges for application functions should be restricted to authorized users only.

 Rationale:

 Ideally, all application source code should be vetted to validate interactions between the application and the logic in the database, but this is usually not possible or feasible with available resources even if the source code is available. The DBA should attempt to obtain assurances from the development organization that this issue has been addressed and should document what has been discovered. The DBA should also inspect all application logic stored in the database (in the form of functions, rules, and triggers) for excessive privileges.

 NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.

Solution

Where possible, revoke SECURITY DEFINER on PostgreSQL functions. To change a SECURITY DEFINER function to SECURITY INVOKER, run the following SQL:

 $ whoami
 root
 $ sudo su - postgres
 $ psql -c 'ALTER FUNCTION [functionname] SECURITY INVOKER;'

 If it is not possible to revoke SECURITY DEFINER, ensure the function can be executed by only the accounts that absolutely need such functionality:

 postgres=# SELECT proname, proacl FROM pg_proc WHERE proname = 'delete_customer';
 proname | proacl
 -----------------+--------------------------------------------------------
 delete_customer | {=X/postgres,postgres=X/postgres,appwriter=X/postgres}
 (1 row)
 postgres=# REVOKE EXECUTE ON FUNCTION delete_customer(integer,boolean) FROM appreader;
 REVOKE
 postgres=# SELECT proname, proacl FROM pg_proc WHERE proname = 'delete_customer';
 proname | proacl
 -----------------+--------------------------------------------------------
 delete_customer | {=X/postgres,postgres=X/postgres}
 (1 row)

 Based on output above, appreader=X/postgres no longer exists in the proacl column results returned from query and confirms appreader is no longer granted execute privilege on the function.

 References:

 https://www.postgresql.org/docs/12/static/catalog-pg-proc.html

 https://www.postgresql.org/docs/12/static/sql-grant.html

 https://www.postgresql.org/docs/12/static/sql-revoke.html

 https://www.postgresql.org/docs/12/static/sql-createfunction.html

See Also

https://workbench.cisecurity.org/files/2536

Item Details

References: CSCv6|5.1, CSCv7|5.1

Plugin: PostgreSQLDB

Control ID: 54f8118878b7df628d492b57706ce4674545c9ca5c36f2ce5db4d88780fba800