CVE-2024-7348 in PostgreSQL
Summary
by MITRE • 08/08/2024
Time-of-check Time-of-use (TOCTOU) race condition in pg_dump in PostgreSQL allows an object creator to execute arbitrary SQL functions as the user running pg_dump, which is often a superuser. The attack involves replacing another relation type with a view or foreign table. The attack requires waiting for pg_dump to start, but winning the race condition is trivial if the attacker retains an open transaction. Versions before PostgreSQL 16.4, 15.8, 14.13, 13.16, and 12.20 are affected.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 10/27/2025
The vulnerability CVE-2024-7348 represents a critical time-of-check time-of-use race condition within PostgreSQL's pg_dump utility that fundamentally undermines the security model of database operations. This flaw exists in the way pg_dump handles object validation during the dump process, creating a window where an attacker can manipulate database objects between the moment when pg_dump checks for object existence and when it actually processes those objects. The vulnerability specifically affects PostgreSQL versions prior to 16.4, 15.8, 14.13, 13.16, and 12.20, indicating a widespread impact across multiple major release lines. From a cybersecurity perspective, this vulnerability maps directly to CWE-367, which defines time-of-check to time-of-use race conditions as a critical weakness where an attacker can exploit the temporal gap between validation and actual use of resources.
The technical exploitation of this vulnerability requires an attacker to have sufficient privileges to create database objects, typically through a database user account that can create relations. The attack mechanism involves replacing a legitimate database object such as a table or materialized view with a malicious view or foreign table that references an SQL function containing attacker-controlled code. When pg_dump encounters this modified object during its processing phase, it executes the SQL functions contained within the malicious view or foreign table with the privileges of the user running pg_dump. Since pg_dump is often executed by superuser accounts with extensive database privileges, this creates a path for privilege escalation and arbitrary code execution within the database context. The attack is particularly effective because the race condition can be won trivially if the attacker maintains an open transaction, allowing them to manipulate the database state before pg_dump processes the objects.
The operational impact of this vulnerability extends beyond simple privilege escalation to encompass potential data exfiltration, data corruption, and complete database compromise. An attacker who successfully exploits this vulnerability can execute arbitrary SQL functions that may include commands to read sensitive data, modify database structures, delete critical information, or even establish persistent backdoors within the database environment. The vulnerability affects database administrators who rely on pg_dump for backup operations, as the utility becomes a vector for unauthorized access to database resources. This represents a significant concern for organizations that use automated backup processes or have pg_dump executed with elevated privileges, as these scenarios provide the perfect conditions for exploitation. The vulnerability also impacts database security architectures that depend on proper privilege separation, as the attack can bypass normal access controls by leveraging the elevated privileges of the pg_dump process itself.
Mitigation strategies for CVE-2024-7348 focus on both immediate patching and operational security improvements. The most effective immediate solution is upgrading to PostgreSQL versions 16.4, 15.8, 14.13, 13.16, or 12.20, which contain the necessary fixes to eliminate the race condition. Organizations should prioritize patching their PostgreSQL installations, particularly those running versions that are no longer supported or have reached end-of-life status. Additional operational mitigations include restricting the execution privileges of pg_dump processes, implementing proper access controls for database object creation, and monitoring for unusual database activity during backup operations. Security teams should also consider implementing database activity monitoring solutions that can detect anomalous behavior during backup processes, as this vulnerability may be used as part of broader attack campaigns targeting database environments. The ATT&CK framework categorizes this vulnerability under T1078 Valid Accounts and T1566 Phishing, as it leverages legitimate database administrative accounts to execute malicious code, making detection more challenging and emphasizing the importance of proper privilege management and monitoring procedures.