Format String Vulnerability in PostgreSQL pg_basebackup

Executive Summary

This vulnerability involves a format string issue in PostgreSQL's pg_basebackup utility. An attacker who has already compromised a server can use backup manifest bytes as a format string to potentially disclose memory contents from pg_basebackup. The attack requires prior access and does not return read bytes directly to the attacker's server, needing additional secrets for success. Integrity impact is unlikely as the formatter does not support %n.

Useful 0 Not Useful 0

Detection Guidance

Detecting this vulnerability requires checking the PostgreSQL version in use. Run 'pg_basebackup --version' to verify if your version is below 18.7, 17.12, 16.16, 15.20, or 14.25. If so, the system is vulnerable.

Useful 0 Not Useful 0

Impact Analysis

If you use an affected PostgreSQL version, an attacker with server access could exploit this to read sensitive memory contents from pg_basebackup. This could lead to unauthorized information disclosure. The impact is limited to confidentiality and requires prior compromise of the server.

Useful 0 Not Useful 0

Compliance Impact

This vulnerability could lead to unauthorized data disclosure, which may violate GDPR's data protection requirements or HIPAA's confidentiality rules. Organizations using affected PostgreSQL versions should patch to avoid compliance risks related to potential memory leaks.

Useful 0 Not Useful 0

Mitigation Strategies

Upgrade PostgreSQL to a patched version (18.7, 17.12, 16.16, 15.20, or 14.25 or later). If immediate upgrade is not possible, restrict access to the server to prevent attackers from exploiting the vulnerability.

Useful 0 Not Useful 0