PostgreSQL Anonymizer: Unbounded memory allocation (DoS) in range-based dummy functions
- 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
PostgreSQL Anonymizer, an extension for the PostgreSQL database system, is affected through its range-based dummy data functions, which do not limit the size of the range they generate. An attacker able to call these functions could exhaust server memory, causing a database process to be terminated and forcing a restart of the whole database cluster.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
PostgreSQL Anonymizer's range-based dummy functions dont constraint the range size. 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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- DALIBO PostgreSQL Anonymizer
From 1 · fixed in 3.3.0