Vert.x STOMP server process client frames that would not send initially a connect frame
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 software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Java / Kotlin (Maven) | io.vertx:vertx-stomp | >= 3.1.0, < 3.9.16, >= 4.0.0, < 4.4.2 | 3.9.16, 4.4.2 |
References
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N- Weakness (CWE)
CWE-287- Platform
- Java / Kotlin (Maven)
- Package
io.vertx:vertx-stomp- Disclosed
- 12.05.2023
- Updated
- 11.10.2026 11:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-gvrq-cg5r-7chp - CC BY 4.0
Vulnerability history: io.vertx:vertx-stomp
All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.
This is the only known vulnerability of this package.
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.