Vert.x STOMP up to 3.9.16/4.4.2 improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in Vert.x STOMP up to 3.9.16/4.4.2. Affected by this issue is some unknown functionality. Executing a manipulation can lead to improper authentication. This vulnerability is tracked as CVE-2023-32081. The attack can be launched remotely. No exploit exists. A patch should be applied to remediate this issue.
Details
A vulnerability was found in Vert.x STOMP up to 3.9.16/4.4.2. It has been declared as critical. This vulnerability affects an unknown functionality. The manipulation with an unknown input leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
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.
The weakness was disclosed 05/12/2023 as GHSA-gvrq-cg5r-7chp. The advisory is available at github.com. This vulnerability was named CVE-2023-32081 since 05/01/2023. The technical details are unknown and an exploit is not available.
Applying the patch 0de4bc5a44ddb57e74d92c445f16456fa03f265b is able to eliminate this problem. The bugfix is ready for download at github.com.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
- 3.9.0
- 3.9.1
- 3.9.2
- 3.9.3
- 3.9.4
- 3.9.5
- 3.9.6
- 3.9.7
- 3.9.8
- 3.9.9
- 3.9.10
- 3.9.11
- 3.9.12
- 3.9.13
- 3.9.14
- 3.9.15
- 3.9.16
- 4.4.0
- 4.4.1
- 4.4.2
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.8
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (GitHub, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 0de4bc5a44ddb57e74d92c445f16456fa03f265b
Timeline
05/01/2023 🔍05/12/2023 🔍
05/12/2023 🔍
05/12/2023 🔍
Sources
Advisory: GHSA-gvrq-cg5r-7chpStatus: Confirmed
CVE: CVE-2023-32081 (🔍)
GCVE (CVE): GCVE-0-2023-32081
GCVE (VulDB): GCVE-100-228922
Entry
Created: 05/12/2023 17:33Changes: 05/12/2023 17:33 (51)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.