Skip to content
Fencer Intel
medium 6.5

CVE-2023-32081 json

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

published 3y ago modified 4mo ago also GHSA-gvrq-cg5r-7chp , EUVD-2023-1547

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 44%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven io.vertx:vertx-stomp 3.9.16, 4.4.2
  • eclipse vert.x_stomp 3.9.16, 4.4.2

Is CVE-2023-32081 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-32081 updated cvss 6.5

vertx-stomp: STOMP server process client frames that would not send initially a connect frame

  • Red Hat JBoss Enterprise Application Platform 7 vertx-stomp vertx-stomp Red Hat JBoss Enterprise Application Platform 8 vertx-stomp vertx-stomp Red Hat JBoss Enterprise Application Platform Expansion Pack vertx-stomp vertx-stomp Red Hat OpenShift Application Runtimes vertx-stomp vertx-stomp
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.51% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven io.vertx:vertx-stomp
>=3.1.0, <3.9.16
>=4.0.0, <4.4.2
3.9.16
4.4.2

Affected products

  • vert-x3 vertx-stomp

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.