Количество 35
Количество 35

BDU:2024-09681
Уязвимость команд SET ROLE, SET SESSION системы управления базами данных PostgreSQL, позволяющая нарушителю повысить свои привилегии и получить доступ к защищаемой информации

ROS-20241211-08
Множественные уязвимости postgresql15-1c

ROS-20241211-07
Множественные уязвимости postgresql-1c

ROS-20241211-06
Множественные уязвимости postgresql16

ROS-20241211-05
Множественные уязвимости postgresql15

ROS-20241211-04
Множественные уязвимости postgresql14

ROS-20241211-03
Множественные уязвимости postgresql13

ROS-20241211-02
Множественные уязвимости postgresql

CVE-2024-10978
Incorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended. An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature. The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker. If that query reacts to current_setting('role') or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION. The attacker does not control which incorrect user ID applies. Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.

CVE-2024-10978
Incorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended. An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature. The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker. If that query reacts to current_setting('role') or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION. The attacker does not control which incorrect user ID applies. Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.

CVE-2024-10978
Incorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended. An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature. The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker. If that query reacts to current_setting('role') or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION. The attacker does not control which incorrect user ID applies. Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.

CVE-2024-10978
CVE-2024-10978
Incorrect privilege assignment in PostgreSQL allows a less-privileged ...
GHSA-37v9-jh5m-f5pg
Incorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended. An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature. The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker. If that query reacts to current_setting('role') or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION. The attacker does not control which incorrect user ID applies. Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.
ELSA-2024-10832
ELSA-2024-10832: postgresql:13 security update (IMPORTANT)
ELSA-2024-10831
ELSA-2024-10831: postgresql:16 security update (IMPORTANT)
ELSA-2024-10830
ELSA-2024-10830: postgresql:15 security update (IMPORTANT)
ELSA-2024-10791
ELSA-2024-10791: postgresql security update (IMPORTANT)
ELSA-2024-10788
ELSA-2024-10788: postgresql:16 security update (IMPORTANT)
ELSA-2024-10787
ELSA-2024-10787: postgresql:15 security update (IMPORTANT)
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
---|---|---|---|---|
![]() | BDU:2024-09681 Уязвимость команд SET ROLE, SET SESSION системы управления базами данных PostgreSQL, позволяющая нарушителю повысить свои привилегии и получить доступ к защищаемой информации | CVSS3: 4.2 | 0% Низкий | 7 месяцев назад |
![]() | ROS-20241211-08 Множественные уязвимости postgresql15-1c | CVSS3: 8.8 | 6 месяцев назад | |
![]() | ROS-20241211-07 Множественные уязвимости postgresql-1c | CVSS3: 8.8 | 6 месяцев назад | |
![]() | ROS-20241211-06 Множественные уязвимости postgresql16 | CVSS3: 8.8 | 6 месяцев назад | |
![]() | ROS-20241211-05 Множественные уязвимости postgresql15 | CVSS3: 8.8 | 6 месяцев назад | |
![]() | ROS-20241211-04 Множественные уязвимости postgresql14 | CVSS3: 8.8 | 6 месяцев назад | |
![]() | ROS-20241211-03 Множественные уязвимости postgresql13 | CVSS3: 8.8 | 6 месяцев назад | |
![]() | ROS-20241211-02 Множественные уязвимости postgresql | CVSS3: 8.8 | 6 месяцев назад | |
![]() | CVE-2024-10978 Incorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended. An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature. The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker. If that query reacts to current_setting('role') or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION. The attacker does not control which incorrect user ID applies. Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected. | CVSS3: 4.2 | 0% Низкий | 7 месяцев назад |
![]() | CVE-2024-10978 Incorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended. An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature. The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker. If that query reacts to current_setting('role') or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION. The attacker does not control which incorrect user ID applies. Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected. | CVSS3: 4.2 | 0% Низкий | 7 месяцев назад |
![]() | CVE-2024-10978 Incorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended. An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature. The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker. If that query reacts to current_setting('role') or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION. The attacker does not control which incorrect user ID applies. Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected. | CVSS3: 4.2 | 0% Низкий | 7 месяцев назад |
![]() | CVSS3: 4.2 | 0% Низкий | 7 месяцев назад | |
CVE-2024-10978 Incorrect privilege assignment in PostgreSQL allows a less-privileged ... | CVSS3: 4.2 | 0% Низкий | 7 месяцев назад | |
GHSA-37v9-jh5m-f5pg Incorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended. An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature. The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker. If that query reacts to current_setting('role') or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION. The attacker does not control which incorrect user ID applies. Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected. | CVSS3: 4.2 | 0% Низкий | 7 месяцев назад | |
ELSA-2024-10832 ELSA-2024-10832: postgresql:13 security update (IMPORTANT) | 7 месяцев назад | |||
ELSA-2024-10831 ELSA-2024-10831: postgresql:16 security update (IMPORTANT) | 7 месяцев назад | |||
ELSA-2024-10830 ELSA-2024-10830: postgresql:15 security update (IMPORTANT) | 7 месяцев назад | |||
ELSA-2024-10791 ELSA-2024-10791: postgresql security update (IMPORTANT) | 6 месяцев назад | |||
ELSA-2024-10788 ELSA-2024-10788: postgresql:16 security update (IMPORTANT) | 7 месяцев назад | |||
ELSA-2024-10787 ELSA-2024-10787: postgresql:15 security update (IMPORTANT) | 7 месяцев назад |
Уязвимостей на страницу