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

GHSA-gvrq-cg5r-7chp

MEDIUM

Vert.x STOMP server process client frames that would not send initially a connect frame

Also known asCVE-2023-32081
Published
May 12, 2023
Updated
Feb 16, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk39th percentile+0.16%
0.00%0.34%0.67%1.01%0.3%0.5%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected
io.vertx:vertx-stompio.vertx:vertx-stomp

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

Impact

A Vert.x STOMP server processes client STOMP frames without checking that the client send an initial CONNECT frame replied with a successful CONNECTED frame. The client can subscribe to a destination or publish message without prior authentication. Any Vert.x STOMP server configured with an authentication handler is impacted.

Patches

The issue is patched in Vert.x 4.4.2 and Vert.x 3.9.16

Workarounds

No trivial workaround.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavenio.vertx:vertx-stomp3.1.0&&< 3.9.163.9.16
Mavenio.vertx:vertx-stomp4.0.0&&< 4.4.24.4.2

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-stomp. 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-stomp to 3.9.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gvrq-cg5r-7chp 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-gvrq-cg5r-7chp 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-gvrq-cg5r-7chp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact A Vert.x STOMP server processes client STOMP frames without checking that the client send an initial CONNECT frame replied with a successful CONNECTED frame. The client can subscribe to a destination or publish message without prior authentication. Any Vert.x STOMP server configured with an authentication handler is impacted. ### Patches The issue is patched in Vert.x 4.4.2 and Vert.x 3.9.16 ### Workarounds No trivial workaround.
O3 Security · Impact-Aware SCA

Is GHSA-gvrq-cg5r-7chp in your dependencies?

O3 detects GHSA-gvrq-cg5r-7chp across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-gvrq-cg5r-7chp: vertx-stomp (Medium 6.5) | O3 Security