Skip to content
Fencer Intel
high 8.8

CVE-2020-35217 json

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

published 5y ago modified 4mo ago also GHSA-9q69-g5gc-9fgf , EUVD-2021-0807

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven io.vertx:vertx-web 4.0.0-milestone5

Is CVE-2020-35217 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-35217 updated cvss 8.8

vertx-web: performs an incorrect CSRF verification

  • Red Hat build of Quarkus vertx-web Red Hat Integration Camel K 1 vertx-web Red Hat Integration Service Registry vertx-web Red Hat OpenShift Application Runtimes vertx-web Red Hat support for Spring Boot vertx-web Red Hat streams for Apache Kafka vertx-web
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven io.vertx:vertx-web
>=4.0.0-milestone1, <4.0.0-milestone5
>=4.0.0-milestone2, <4.0.0-milestone5
>=4.0.0-milestone3, <4.0.0-milestone5
>=4.0.0-milestone4, <4.0.0-milestone5
4.0.0-milestone5

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.