PostgreSQL Anonymizer: Unbounded image-decode memory allocation (DoS) in anon.image_blur()

Özet

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

PostgreSQL Anonymizer's anon.image_blur() function doesn't check the declared dimension of the provided image, allowing an attacker to provide a small image with enormous declared dimensions. This vulnerability can be exploited to exhaust the memory of a backend and OOM-kill it (when ovecommit is on), which results in a cluster-wide crash recovery. 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/691 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