Skip to content

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 Nov 11, 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

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.

References

@vietj vietj published to vert-x3/vertx-stomp May 12, 2023
Published by the National Vulnerability Database May 12, 2023
Published to the GitHub Advisory Database May 12, 2023
Reviewed May 12, 2023
Last updated Nov 11, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS score

0.109%
(45th percentile)

Weaknesses

CVE ID

CVE-2023-32081

GHSA ID

GHSA-gvrq-cg5r-7chp

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.