PostgreSQL Anonymizer: The secret salt and shift of anon are readable by any role in pg_roles or pg_db_role_setting
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.3.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The PostgreSQL Anonymizer extension (anon) is affected. Its secret salt and shift values, which are used for data masking, can be read by any database role through the pg_roles and pg_db_role_setting system catalogs when they were configured at the database or role level, bypassing the restriction normally placed on the SHOW command.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
PostgreSQL restricts acces to the salt and shift via the `SHOW` command for users not member of `pg_read_all_settings`. But they are visible in `pg_db_role_setting` or `pg_roles` if they were set on the database, user or both. PostgreSQL Anonymizer's documentation recommends to use ALTER DATABASE / ALTER ROLE for the salt. The problem is resolved in PostgreSQL Anonymizer 3.3.0 and later versions.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- DALIBO PostgreSQL Anonymizer
From 1 · fixed in 3.3.0