Technical impact
PostgreSQL Anonymizer stores a secret salt and shift value that are meant to protect data. The current implementation incorrectly allows any role that can query the system catalogs pg_roles or pg_db_role_setting to view these values, exposing them as a database secret. This vulnerability is a classic information‑disclosure weakness (CWE‑200) that could let an attacker reverse the anonymization process and recover the original data, effectively breaching confidentiality.
Affected Systems
Dalibo’s PostgreSQL Anonymizer extension is affected. All versions before 3.3.0 contain the flaw because the salt and shift are stored in database‑level settings that are readable by any role with access to pg_roles or pg_db_role_setting. The issue is fixed in 3.3.0 and later releases. Organizations using older Anonymizer versions on PostgreSQL databases, particularly those with permissive role configurations, are at risk.
Risk and Exploitability
The CVSS score of 5.7 indicates moderate severity. Exploitation requires an authenticated database user that can read the system catalogs; the most likely scenario is an internal user with broad privileges or a compromised account. Since EPSS is unavailable and the vulnerability is not in the KEV catalog, the current public exploitation probability is unknown. Nevertheless, because the exposed data can reveal sensitive information, a moderate risk assessment is prudent.