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

Уязвимость компонента Schema Handler системы управления базами данных PostgreSQL, позволяющая нарушителю обойти ограничения безопасности

ALT-PU-2023-1860: package `postgresql15-1C` update to version 15.3-alt0.p10.1

ALT-PU-2023-1859: package `postgresql14` update to version 14.8-alt0.p10.1

ALT-PU-2023-1858: package `postgresql13` update to version 13.11-alt0.p10.1

ALT-PU-2023-1857: package `postgresql12` update to version 12.15-alt0.p10.1

ALT-PU-2023-1856: package `postgresql11` update to version 11.20-alt0.p10.1

ALT-PU-2023-1855: package `postgresql15` update to version 15.3-alt0.p10.1

ALT-PU-2023-1780: package `postgresql15-1C` update to version 15.3-alt1

ALT-PU-2023-1779: package `postgresql14` update to version 14.8-alt1

ALT-PU-2023-1778: package `postgresql13` update to version 13.11-alt1

ALT-PU-2023-1777: package `postgresql12` update to version 12.15-alt1

ALT-PU-2023-1776: package `postgresql11` update to version 11.20-alt1

ALT-PU-2023-1775: package `postgresql15` update to version 15.3-alt1

Множественные уязвимости postgresql13

Множественные уязвимости postgresql

Row security policies disregard user ID changes after inlining; PostgreSQL could permit incorrect policies to be applied in certain cases where role-specific policies are used and a given query is planned under one role and then executed under other roles. This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs. Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications. This affects only databases that have used CREATE POLICY to define a row security policy.

Row security policies disregard user ID changes after inlining; PostgreSQL could permit incorrect policies to be applied in certain cases where role-specific policies are used and a given query is planned under one role and then executed under other roles. This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs. Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications. This affects only databases that have used CREATE POLICY to define a row security policy.

Row security policies disregard user ID changes after inlining; PostgreSQL could permit incorrect policies to be applied in certain cases where role-specific policies are used and a given query is planned under one role and then executed under other roles. This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs. Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications. This affects only databases that have used CREATE POLICY to define a row security policy.

Row security policies disregard user ID changes after inlining; Postgr ...