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

exploitDog

github логотип

GHSA-9q69-g5gc-9fgf

Опубликовано: 22 апр. 2021
Источник: github
Github: Прошло ревью
CVSS3: 8.8

Описание

Cross-Site Request Forgery in Vert.x-Web framework

Vert.x-Web framework v4.0 milestone 1-4 does not perform a correct CSRF verification. Instead of comparing the CSRF token in the request with the CSRF token in the cookie, it compares the CSRF token in the cookie against a CSRF token that is stored in the session. An attacker does not even need to provide a CSRF token in the request because the framework does not consider it. The cookies are automatically sent by the browser and the verification will always succeed, leading to a successful CSRF attack.

Пакеты

Наименование

io.vertx:vertx-web

maven
Затронутые версииВерсия исправления

= 4.0.0-milestone1

4.0.0-milestone5

Наименование

io.vertx:vertx-web

maven
Затронутые версииВерсия исправления

= 4.0.0-milestone2

4.0.0-milestone5

Наименование

io.vertx:vertx-web

maven
Затронутые версииВерсия исправления

= 4.0.0-milestone3

4.0.0-milestone5

Наименование

io.vertx:vertx-web

maven
Затронутые версииВерсия исправления

= 4.0.0-milestone4

4.0.0-milestone5

EPSS

Процентиль: 36%
0.00154
Низкий

8.8 High

CVSS3

Дефекты

CWE-352

Связанные уязвимости

CVSS3: 8.8
redhat
около 5 лет назад

Vert.x-Web framework v4.0 milestone 1-4 does not perform a correct CSRF verification. Instead of comparing the CSRF token in the request with the CSRF token in the cookie, it compares the CSRF token in the cookie against a CSRF token that is stored in the session. An attacker does not even need to provide a CSRF token in the request because the framework does not consider it. The cookies are automatically sent by the browser and the verification will always succeed, leading to a successful CSRF attack.

CVSS3: 8.8
nvd
около 5 лет назад

Vert.x-Web framework v4.0 milestone 1-4 does not perform a correct CSRF verification. Instead of comparing the CSRF token in the request with the CSRF token in the cookie, it compares the CSRF token in the cookie against a CSRF token that is stored in the session. An attacker does not even need to provide a CSRF token in the request because the framework does not consider it. The cookies are automatically sent by the browser and the verification will always succeed, leading to a successful CSRF attack.

EPSS

Процентиль: 36%
0.00154
Низкий

8.8 High

CVSS3

Дефекты

CWE-352