Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-9q69-g5gc-9fgf

HIGH

GHSA-9q69-g5gc-9fgf is a high-severity (CVSS 8.8) Cross-Site Request Forgery (CSRF) vulnerability in io.vertx:vertx-web. O3 Security confirms whether GHSA-9q69-g5gc-9fgf is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Also known asCVE-2020-35217
Published
Apr 22, 2021
Updated
Nov 8, 2023
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed

Blast Radius

4 pkgs affected
io.vertx:vertx-webio.vertx:vertx-webio.vertx:vertx-webio.vertx:vertx-web

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
Mavenio.vertx:vertx-web4.0.0-milestone1&&< 4.0.0-milestone54.0.0-milestone5
Mavenio.vertx:vertx-web4.0.0-milestone2&&< 4.0.0-milestone54.0.0-milestone5
Mavenio.vertx:vertx-web4.0.0-milestone3&&< 4.0.0-milestone54.0.0-milestone5
Mavenio.vertx:vertx-web4.0.0-milestone4&&< 4.0.0-milestone54.0.0-milestone5

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.vertx:vertx-web. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update io.vertx:vertx-web to 4.0.0-milestone5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9q69-g5gc-9fgf is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-9q69-g5gc-9fgf is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-9q69-g5gc-9fgf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-9q69-g5gc-9fgf in your dependencies?

O3 detects GHSA-9q69-g5gc-9fgf across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.