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

Integer wraparound 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. In applications that pass gigabyte-scale user inputs to the relevant database functions, the application input provider may achieve a segmentation fault. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

Integer wraparound 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. In applications that pass gigabyte-scale user inputs to the relevant database functions, the application input provider may achieve a segmentation fault. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

PostgreSQL server undersizes allocations, via integer wraparound

Integer wraparound in multiple PostgreSQL server features allows an un ...

Covert timing channel in comparison of MD5-hashed password in PostgreSQL authentication allows an attacker to recover user credentials sufficient to authenticate. This does not affect scram-sha-256 passwords, the default in all supported releases. However, current databases may have MD5-hashed passwords originating in upgrades from PostgreSQL 13 or earlier. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

Covert timing channel in comparison of MD5-hashed password in PostgreSQL authentication allows an attacker to recover user credentials sufficient to authenticate. This does not affect scram-sha-256 passwords, the default in all supported releases. However, current databases may have MD5-hashed passwords originating in upgrades from PostgreSQL 13 or earlier. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

Covert timing channel in comparison of MD5-hashed password in PostgreSQL authentication allows an attacker to recover user credentials sufficient to authenticate. This does not affect scram-sha-256 passwords, the default in all supported releases. However, current databases may have MD5-hashed passwords originating in upgrades from PostgreSQL 13 or earlier. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

PostgreSQL discloses MD5-hashed passwords via covert timing channel

Covert timing channel in comparison of MD5-hashed password in PostgreS ...

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

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