PostgreSQL Anonymizer v2.0 and v2.1 contain a vulnerability that allows a masked user to bypass the masking rules defined on a table and read the original data using a database cursor or the --insert option of pg_dump. This problem occurs only when dynamic masking is enabled, which is not the default setting. The problem is resolved in version 2.2.1
Metrics
Affected Vendors & Products
References
Link | Providers |
---|---|
https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/531 |
![]() ![]() |
History
Thu, 05 Jun 2025 19:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|
Wed, 04 Jun 2025 21:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | PostgreSQL Anonymizer v2.0 and v2.1 contain a vulnerability that allows a masked user to bypass the masking rules defined on a table and read the original data using a database cursor or the --insert option of pg_dump. This problem occurs only when dynamic masking is enabled, which is not the default setting. The problem is resolved in version 2.2.1 | |
Title | Cursor allows PostgreSQL Anonymizer masked user to gain unauthorized access to authentic data | |
Weaknesses | CWE-200 | |
References |
| |
Metrics |
cvssV3_1
|

Status: PUBLISHED
Assigner: PostgreSQL
Published: 2025-06-04T21:34:47.358Z
Updated: 2025-06-05T18:10:03.492Z
Reserved: 2025-06-04T18:41:30.661Z
Link: CVE-2025-5690

Updated: 2025-06-05T18:09:57.103Z

Status : Awaiting Analysis
Published: 2025-06-04T22:15:26.470
Modified: 2025-06-05T20:12:23.777
Link: CVE-2025-5690

No data.