PostgreSQL Anonymizer vulnerabilities

PostgreSQL Anonymizer contains a vulnerability that allows unprivileged masked users to repeatedly call anon.hash() and collect (seed, hash_output) pairs to perform an offline brute-force attack and deduce the salt. The issue is fixed in version 3.2.3.

PostgreSQL Anonymizer contains a vulnerability in the anon.anonymize_database_parallel() function that allows a table owner to execute arbitrary code with superuser privileges. The issue is fixed in version 3.2.0 and later.

PostgreSQL Anonymizer contains a SQL injection vulnerability in two import functions. A user can create a malicious JSON document with specially crafted object names. If a superuser calls anon.import_database_rules() or anon.import_roles_rules(), malicious code is executed with superuser privileges. Fixed in version 3.1.4 and later.

PostgreSQL Anonymizer contains a vulnerability allowing unprivileged masked users to execute arbitrary code by abusing operators, domain casts, or view subqueries carrying untrusted expressions. When evaluated in the masking context, malicious code can run with elevated privileges. Fixed in version 3.1.4 and later.

A vulnerability in PostgreSQL Anonymizer allows unprivileged masked users to repeatedly call the anon.hash() function and collect (seed, hash_output) pairs to perform an offline brute-force attack and deduce the salt.

PostgreSQL Anonymizer contains a vulnerability that allows a user to gain superuser privileges by creating a JSON document and placing malicious code inside a particular key-value pair. If a superuser calls the import_database_rules() or import_roles_rules() functions, the malicious code is executed with superuser privileges.