Cross-Site Request Forgery in Vert.x-Web framework
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| io.vertx:vertx-web Maven |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| io.vertx:vertx-web Maven |
|
|
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.
From the CVE record · mitre
Vert.x-Web 4.0 milestones 1–4 compare the CSRF cookie token with a session token instead of checking the token in the request. An attacker can carry out a CSRF attack without supplying a request token when a browser automatically sends the cookie.
Engineers using Maven package io.vertx:vertx-web versions 4.0.0-milestone1 through 4.0.0-milestone4 should check their dependencies.