Headline
GHSA-gvrq-cg5r-7chp: 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.
- GitHub Advisory Database
- GitHub Reviewed
- CVE-2023-32081
Vert.x STOMP server process client frames that would not send initially a connect frame
Moderate severity GitHub Reviewed Published May 12, 2023 in vert-x3/vertx-stomp • Updated May 12, 2023
Package
maven io.vertx:vertx-stomp (Maven)
Affected versions
>= 3.1.0, < 3.9.16
>= 4.0.0, < 4.4.2
Patched versions
3.9.16
4.4.2
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.
References
- GHSA-gvrq-cg5r-7chp
- https://nvd.nist.gov/vuln/detail/CVE-2023-32081
- vert-x3/vertx-stomp@0de4bc5
Published to the GitHub Advisory Database
May 12, 2023
Last updated
May 12, 2023
Related news
Vert.x STOMP is a vert.x implementation of the STOMP specification that provides a STOMP server and client. From versions 3.1.0 until 3.9.16 and 4.0.0 until 4.4.2, 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. The issue is patched in Vert.x 3.9.16 and 4.4.2. There are no trivial workarounds.