PostgreSQL libpq lo_* functions let server superuser overwrite client stack memory
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 14.23, 15.18, 16.14 and 2 more.
Use of inherently dangerous function PQfn(..., result_is_int=0, ...) in PostgreSQL libpq lo_export(), lo_read(), lo_lseek64(), and lo_tell64() functions allows the server superuser to overwrite a client stack buffer with an arbitrarily-large response. Like gets(), PQfn(..., result_is_int=0, ...) stores arbitrary-length, server-determined data into a buffer of unspecified size. Because both the \lo_export command in psql and pg_dump call lo_read(), the server superuser can overwrite pg_dump or psql stack memory. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| postgresql | postgresql | <14.23, >=15.0 <15.18, >=16.0 <16.14, >=17.0 <17.10, >=18.0 <18.4 | 14.23, 15.18, 16.14, 17.10, 18.4 |
| <14.23, >=15 <15.18, >=16 <16.14, >=17 <17.10, >=18 <18.4 | 14.23, 15.18, 16.14, 17.10, 18.4 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket