Логотип exploitDog
bind:CVE-2022-40816
Консоль
Логотип exploitDog

exploitDog

bind:CVE-2022-40816

Количество 3

Количество 3

nvd логотип

CVE-2022-40816

больше 3 лет назад

Zammad 5.2.1 is vulnerable to Incorrect Access Control. Zammad's asset handling mechanism has logic to ensure that customer users are not able to see personal information of other users. This logic was not effective when used through a web socket connection, so that a logged-in attacker would be able to fetch personal data of other users by querying the Zammad API. This issue is fixed in , 5.2.2.

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

CVE-2022-40816

больше 3 лет назад

Zammad 5.2.1 is vulnerable to Incorrect Access Control. Zammad's asset ...

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

GHSA-gwqr-42v8-7m7q

больше 3 лет назад

Zammad 5.2.1 is vulnerable to Incorrect Access Control. Zammad's asset handling mechanism has logic to ensure that customer users are not able to see personal information of other users. This logic was not effective when used through a web socket connection, so that a logged-in attacker would be able to fetch personal data of other users by querying the Zammad API. This issue is fixed in , 5.2.2.

CVSS3: 6.5
EPSS: Низкий

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

Уязвимость
CVSS
EPSS
Опубликовано
nvd логотип
CVE-2022-40816

Zammad 5.2.1 is vulnerable to Incorrect Access Control. Zammad's asset handling mechanism has logic to ensure that customer users are not able to see personal information of other users. This logic was not effective when used through a web socket connection, so that a logged-in attacker would be able to fetch personal data of other users by querying the Zammad API. This issue is fixed in , 5.2.2.

CVSS3: 6.5
0%
Низкий
больше 3 лет назад
debian логотип
CVE-2022-40816

Zammad 5.2.1 is vulnerable to Incorrect Access Control. Zammad's asset ...

CVSS3: 6.5
0%
Низкий
больше 3 лет назад
github логотип
GHSA-gwqr-42v8-7m7q

Zammad 5.2.1 is vulnerable to Incorrect Access Control. Zammad's asset handling mechanism has logic to ensure that customer users are not able to see personal information of other users. This logic was not effective when used through a web socket connection, so that a logged-in attacker would be able to fetch personal data of other users by querying the Zammad API. This issue is fixed in , 5.2.2.

CVSS3: 6.5
0%
Низкий
больше 3 лет назад

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