HighGHSA-9q69-g5gc-9fgfCVE-2020-35217

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

Published 22 Apr 2021 · Updated 8 Nov 2023

Is your project on an affected io.vertx:vertx-web?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=4.0.0-milestone1 <4.0.0-milestone5
Fixed in
4.0.0-milestone5
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=io.vertx:vertx-web -DdepVersion=4.0.0-milestone5 -DforceVersion=true
Affected
>=4.0.0-milestone2 <4.0.0-milestone5
Fixed in
4.0.0-milestone5
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=io.vertx:vertx-web -DdepVersion=4.0.0-milestone5 -DforceVersion=true
Affected
>=4.0.0-milestone3 <4.0.0-milestone5
Fixed in
4.0.0-milestone5
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=io.vertx:vertx-web -DdepVersion=4.0.0-milestone5 -DforceVersion=true
Affected
>=4.0.0-milestone4 <4.0.0-milestone5
Fixed in
4.0.0-milestone5
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=io.vertx:vertx-web -DdepVersion=4.0.0-milestone5 -DforceVersion=true

Details

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.

Is GHSA-9q69-g5gc-9fgf in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected io.vertx:vertx-web, and gives you the command that fixes it.

More advisories for io.vertx:vertx-web

  • LowCVE-2025-11966Vert.x-Web vulnerable to Stored Cross-site Scripting in directory listings via file names · 22 Oct 2025
  • MediumCVE-2025-11965Vert.x-Web Access Control Flaw in StaticHandler’s Hidden File Protection for Files Under Hidden Directories · 22 Oct 2025
  • MediumCVE-2023-24815StaticHandler disclosure of classpath resources on Windows when mounted on a wildcard route · 10 Feb 2023
  • CriticalCVE-2019-17640Path Traversal in Eclipse Vert · 10 Feb 2022
  • CriticalCVE-2018-12542Eclipse Vert.x does not properly neutralize '' (forward slashes) sequences that can resolve to an external location · 17 Oct 2018
  • HighCVE-2018-12540High severity vulnerability that affects io.vertx:vertx-web · 17 Oct 2018
io.vertx:vertx-web security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.