CVE-2020-35217

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.

Published: 2021-01-20 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-35217 is rated Moderate Risk (50.6/100): CVSS High severity, with low exploitation likelihood (EPSS 0.58%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-35217

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.15% 0.58% +0.43%
2 2025-03-30 0.12% 0.15% +0.03%
3 2025-03-29 — 0.12% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-35217

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2020-35217

GitHub Security Advisory for CVE-2020-35217

GHSA-9q69-g5gc-9fgf · Severity: high · Ecosystem: maven — Cross-Site Request Forgery in Vert.x-Web framework

OS Trackers for CVE-2020-35217

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2020-35217

Affected software / configurations for CVE-2020-35217

Vendor Product Version Raw CPE
eclipse vert.x-web 4.0.0 cpe:2.3:a:eclipse:vert.x-web:4.0.0:milestone1:*:*:*:*:*:*
eclipse vert.x-web 4.0.0 cpe:2.3:a:eclipse:vert.x-web:4.0.0:milestone2:*:*:*:*:*:*
eclipse vert.x-web 4.0.0 cpe:2.3:a:eclipse:vert.x-web:4.0.0:milestone3:*:*:*:*:*:*
eclipse vert.x-web 4.0.0 cpe:2.3:a:eclipse:vert.x-web:4.0.0:milestone4:*:*:*:*:*:*

References for CVE-2020-35217

URL Tags
https://github.com/vert-x3/vertx-web/pull/1613 Patch Third Party Advisory
cvelogic Threat Intelligence