Поиск уязвимостей

ALT-PU-2026-8091: package `postgresql15-1C` update to version 15.15-alt0.p10.5

ALT-PU-2026-7952: package `postgresql14` update to version 14.23-alt0.p10.1

ALT-PU-2026-7949: package `postgresql15` update to version 15.18-alt0.p10.1

ALT-PU-2026-7738: package `postgresql14` update to version 14.23-alt1

ALT-PU-2026-7736: package `postgresql15` update to version 15.18-alt1

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.

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.

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.

PostgreSQL libpq lo_* functions let server superuser overwrite client stack memory

Use of inherently dangerous function PQfn(..., result_is_int=0, ...) i ...

ALT-PU-2026-7951: package `postgresql16` update to version 16.14-alt0.p10.1

ALT-PU-2026-7740: package `postgresql16` update to version 16.14-alt1

ALT-PU-2026-7953: package `postgresql17` update to version 17.10-alt0.p10.1

ALT-PU-2026-7948: package `postgresql17-1C` update to version 17.7-alt0.p11.7

ALT-PU-2026-7741: package `postgresql17` update to version 17.10-alt1

ALT-PU-2026-7946: package `postgresql18-1C` update to version 18.4-alt1

ALT-PU-2026-7739: package `postgresql18` update to version 18.4-alt1

Important: libpq security update

Important: libpq security update

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.