Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

Количество 55

Количество 55

suse-cvrf логотип

SUSE-SU-2024:4099-1

почти 2 года назад

Security update for postgresql12

EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2024:4098-1

почти 2 года назад

Security update for postgresql15

EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2024:4097-1

почти 2 года назад

Security update for postgresql12

EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2024:4096-1

почти 2 года назад

Security update for postgresql14

EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2024:4095-1

почти 2 года назад

Security update for postgresql15

EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2024:4063-1

почти 2 года назад

Security update for postgresql, postgresql16, postgresql17

EPSS: Низкий
redos логотип

ROS-20241211-08

почти 2 года назад

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

CVSS3: 8.8
EPSS: Низкий
redos логотип

ROS-20241211-07

почти 2 года назад

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

CVSS3: 8.8
EPSS: Низкий
redos логотип

ROS-20241211-06

почти 2 года назад

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

CVSS3: 8.8
EPSS: Низкий
redos логотип

ROS-20241211-05

почти 2 года назад

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

CVSS3: 8.8
EPSS: Низкий
redos логотип

ROS-20241211-04

почти 2 года назад

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

CVSS3: 8.8
EPSS: Низкий
redos логотип

ROS-20241211-03

почти 2 года назад

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

CVSS3: 8.8
EPSS: Низкий
redos логотип

ROS-20241211-02

почти 2 года назад

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

CVSS3: 8.8
EPSS: Низкий
ubuntu логотип

CVE-2024-10978

почти 2 года назад

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
EPSS: Низкий
redhat логотип

CVE-2024-10978

почти 2 года назад

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
EPSS: Низкий
nvd логотип

CVE-2024-10978

почти 2 года назад

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
EPSS: Низкий
msrc логотип

CVE-2024-10978

почти 2 года назад

PostgreSQL SET ROLE SET SESSION AUTHORIZATION reset to wrong user ID

CVSS3: 4.2
EPSS: Низкий
debian логотип

CVE-2024-10978

почти 2 года назад

Incorrect privilege assignment in PostgreSQL allows a less-privileged ...

CVSS3: 4.2
EPSS: Низкий
github логотип

GHSA-37v9-jh5m-f5pg

почти 2 года назад

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
EPSS: Низкий
fstec логотип

BDU:2024-09681

почти 2 года назад

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

CVSS3: 4.2
EPSS: Низкий

Уязвимостей на страницу

Уязвимость
CVSS
EPSS
Опубликовано
suse-cvrf логотип
SUSE-SU-2024:4099-1

Security update for postgresql12

почти 2 года назад
suse-cvrf логотип
SUSE-SU-2024:4098-1

Security update for postgresql15

почти 2 года назад
suse-cvrf логотип
SUSE-SU-2024:4097-1

Security update for postgresql12

почти 2 года назад
suse-cvrf логотип
SUSE-SU-2024:4096-1

Security update for postgresql14

почти 2 года назад
suse-cvrf логотип
SUSE-SU-2024:4095-1

Security update for postgresql15

почти 2 года назад
suse-cvrf логотип
SUSE-SU-2024:4063-1

Security update for postgresql, postgresql16, postgresql17

почти 2 года назад
redos логотип
ROS-20241211-08

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

CVSS3: 8.8
почти 2 года назад
redos логотип
ROS-20241211-07

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

CVSS3: 8.8
почти 2 года назад
redos логотип
ROS-20241211-06

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

CVSS3: 8.8
почти 2 года назад
redos логотип
ROS-20241211-05

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

CVSS3: 8.8
почти 2 года назад
redos логотип
ROS-20241211-04

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

CVSS3: 8.8
почти 2 года назад
redos логотип
ROS-20241211-03

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

CVSS3: 8.8
почти 2 года назад
redos логотип
ROS-20241211-02

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

CVSS3: 8.8
почти 2 года назад
ubuntu логотип
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
1%
Низкий
почти 2 года назад
redhat логотип
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
1%
Низкий
почти 2 года назад
nvd логотип
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
1%
Низкий
почти 2 года назад
msrc логотип
CVE-2024-10978

PostgreSQL SET ROLE SET SESSION AUTHORIZATION reset to wrong user ID

CVSS3: 4.2
1%
Низкий
почти 2 года назад
debian логотип
CVE-2024-10978

Incorrect privilege assignment in PostgreSQL allows a less-privileged ...

CVSS3: 4.2
1%
Низкий
почти 2 года назад
github логотип
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
1%
Низкий
почти 2 года назад
fstec логотип
BDU:2024-09681

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

CVSS3: 4.2
1%
Низкий
почти 2 года назад

Уязвимостей на страницу