Skip to content

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

High severity GitHub Reviewed Published Apr 22, 2021 to the GitHub Advisory Database • Updated Feb 1, 2023

Package

maven io.vertx:vertx-web (Maven)

Affected versions

= 4.0.0-milestone1
= 4.0.0-milestone2
= 4.0.0-milestone3
= 4.0.0-milestone4

Patched versions

4.0.0-milestone5
4.0.0-milestone5
4.0.0-milestone5
4.0.0-milestone5

Description

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.

References

Published by the National Vulnerability Database Jan 20, 2021
Reviewed Apr 20, 2021
Published to the GitHub Advisory Database Apr 22, 2021
Last updated Feb 1, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.088%
(39th percentile)

Weaknesses

CVE ID

CVE-2020-35217

GHSA ID

GHSA-9q69-g5gc-9fgf

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.