CVE-2020-5419
CVE-2020-5419 — RabbitMQ arbitrary code execution using local binary planting
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.
Published Updated Sources: cvelistV5, pivotal
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
0%
chance of exploitation in 30 days
CVSS base
6.7
MEDIUM
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 6.7 | CVSS 3.0 | MEDIUM | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-427
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable
- T1574.009Hijack Execution Flow: Path Interception by Unquoted Path
- T1574.001Hijack Execution Flow: DLL search order hijacking
References
1 on the record
- tanzu.vmware.com/security/cve-2020-5419
x_refsource_CONFIRM
Elsewhere on this site
- vmware tanzuevery CVE for this vendor
- CWE-427other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.