RabbitMQ up to 3.8.6 Security Vulnerability uncontrolled search path
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in RabbitMQ up to 3.8.6 and classified as critical. The affected element is an unknown function of the component Security Vulnerability. Performing a manipulation results in uncontrolled search path. This vulnerability is known as CVE-2020-5419. Attacking locally is a requirement. No exploit is available. The affected component should be upgraded.
Details
A vulnerability was found in RabbitMQ up to 3.8.6. It has been classified as critical. This affects an unknown part of the component Security Vulnerability. The manipulation with an unknown input leads to a uncontrolled search path vulnerability. CWE is classifying the issue as CWE-427. The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
RabbitMQ versions 3.8.x prior to 3.8.7 are prone to a Windows-specific binary planting security vulnerability that allows for arbitrary code execution. An attacker with write privileges to the RabbitMQ installation directory and local access on Windows could carry out a local binary hijacking (planting) attack and execute arbitrary code.
The weakness was published 08/31/2020 (Website). The advisory is shared at tanzu.vmware.com. This vulnerability is uniquely identified as CVE-2020-5419 since 01/03/2020. An attack has to be approached locally. The exploitation requires an enhanced level of successful authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1574 for this issue.
Upgrading eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.8
VulDB Base Score: 4.2
VulDB Temp Score: 4.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.7
NVD Vector: 🔍
CNA Base Score: 6.7
CNA Vector (Pivotal Software, 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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Uncontrolled search pathCWE: CWE-427 / CWE-426
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
01/03/2020 🔍08/31/2020 🔍
08/31/2020 🔍
04/02/2025 🔍
Sources
Advisory: tanzu.vmware.comStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2020-5419 (🔍)
GCVE (CVE): GCVE-0-2020-5419
GCVE (VulDB): GCVE-100-160485
Entry
Created: 08/31/2020 22:16Updated: 04/02/2025 20:18
Changes: 08/31/2020 22:16 (38), 08/31/2020 22:21 (11), 11/12/2020 07:13 (1), 11/12/2020 07:22 (1), 04/02/2025 20:18 (35)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.