PostgreSQL vulnerabilities

In PostgreSQL libpq, the lo_export(), lo_read(), lo_lseek64(), and lo_tell64() functions use the inherently dangerous PQfn(..., result_is_int=0, ...) function, allowing the server superuser to overwrite a client stack buffer with arbitrarily-large data. Like gets(), PQfn stores arbitrary-length data into a buffer of unspecified size. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

An integer wraparound vulnerability in multiple PostgreSQL server features allows an unprivileged database user to cause the server to undersize an allocation and write out-of-bounds. This may execute arbitrary code as the operating system user running the database. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

The DataRow.Decode function fails to properly validate field lengths. A malicious PostgreSQL server can send a DataRow message with a negative field length, causing a slice bounds out of range panic.

A heap buffer overflow in PostgreSQL pg_trgm allows a database user to achieve unknown impacts via a crafted input string. The attacker has limited control over byte patterns, but privilege escalation is not ruled out. Affects versions 18.0 and 18.1.

Missing validation of multibyte character length in PostgreSQL text manipulation allows a database user to issue crafted queries that achieve a buffer overrun. That suffices to execute arbitrary code as the operating system user running the database.

Missing input type validation in the PostgreSQL intarray extension selectivity estimator function allows an object creator to execute arbitrary code as the OS user running the database. Versions before 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

Missing authorization in PostgreSQL CREATE STATISTICS command allows a table owner to cause denial of service against other CREATE STATISTICS users by creating an object in any schema. A later CREATE STATISTICS for the same name by a user with CREATE privilege would fail. Affects versions before PostgreSQL 18.1, 17.7, 16.11, 15.15, 14.20, and 13.23.

A memory disclosure vulnerability was found in PostgreSQL that allows remote users to access sensitive information by exploiting certain aggregate function calls with 'unknown'-type arguments. Handling 'unknown'-type values from string literals without type designation can disclose bytes, potentially revealing notable and confidential information.

A vulnerability was found in PostgreSQL with the use of the MERGE command, which fails to test new rows against row security policies defined for UPDATE and SELECT. A user could store such rows that are forbidden by UPDATE and SELECT policies but not by INSERT policies.

A vulnerability was found in PostgreSQL requiring permission to create non-temporary objects in at least one schema, the ability to lure or wait for an administrator to create or update an affected extension in that schema, and the ability to lure or wait for a victim to use the targeted object in CREATE OR REPLACE or CREATE IF NOT EXISTS. With all three prerequisites met, an attacker can run arbitrary code as the victim role, which may be a superuser.

PostgreSQL 10.x before 10.1, 9.6.x before 9.6.6, 9.5.x before 9.5.10, 9.4.x before 9.4.15, 9.3.x before 9.3.20, and 9.2.x before 9.2.24 runs under a non-root operating system account, and database superusers have effective ability to run arbitrary code under that system account. Packager-authored startup implementations use a log file name that the database superuser can replace with a symbolic link, and as root they open(), chmod() and/or chown() this log file name.

Insecure directory permissions in RPM distribution for PostgreSQL allow local users to gain privileges by reading a plaintext password file.