PostgreSQL Anonymizer: The secret salt and shift of anon are readable by any role in pg_roles or pg_db_role_setting

Özet

Türkçe özeti henüz hazır değil; şimdilik kaynağın kendi açıklamasını gösteriyoruz.

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.

Etkilenen sürümler1 yazılım

Kaynaklar3 kaynak

• CVE.org kaydı
• NVD kaydı
• gitlab.com/dalibo/postgresql_anonymizer/-/issues/694 Diğer

Kayıt geçmişi

1. 28 Eki 2026 20:31Yayımlandı

İlgili açıklar

• 4,3 CVE-2026-110182PostgreSQL Anonymizer: anon.partial() and anon.partial_email() can reveal the whole data
• 4,3 CVE-2026-110183PostgreSQL Anonymizer: statistics can expose some of the original data after statistic masking
• 6,5 CVE-2026-105620PostgreSQL Anonymizer: A masked role reads the authentic data of masked tables through a masking rule with a sub-query
• 6,5 CVE-2026-110181PostgreSQL Anonymizer: Function declared with SQL-standard syntax leak anonymized data
• 5,7 CVE-2026-105618PostgreSQL Anonymizer: Masked partitions and child tables are not masked when they are queried through their parent
• 4,8 CVE-2026-105619PostgreSQL Anonymizer: Masking rules of the tables are not applied through security_invoker views