LiveActive security incident?Get immediate response
CVE Record

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.

MediumCVSS 6.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-5419 affects RabbitMQ on Windows. A local attacker who already has write access to the RabbitMQ installation directory could plant a binary and cause arbitrary code to run. This is not a remote internet-facing bug, but it can turn weak local permissions into full compromise of the RabbitMQ host.

Executive priority

Treat this as a controlled remediation item, not an emergency remote-exploit event. Prioritize Windows RabbitMQ servers with broad local access, weak installation-directory permissions, or high business impact.

Technical view

The issue is a Windows-specific CWE-427 binary planting vulnerability in RabbitMQ 3.8.x before 3.8.7, with source data also listing 3.7 and 3.8 as affected. CVSS 6.7 reflects local access, low attack complexity, high privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on Windows RabbitMQ deployments running affected 3.7 or 3.8 versions where non-administrative users, service accounts, or deployment tooling can write to the RabbitMQ installation directory.

Exploitation context

The source bundle does not indicate known active exploitation, and KEV is false. Exploitation requires local Windows access plus write privileges to the RabbitMQ installation directory, so risk depends heavily on endpoint access controls and filesystem permissions.

Researcher notes

Evidence supports local arbitrary code execution through binary planting. The main uncertainty is version scope because the description names 3.8.x before 3.8.7 while affected metadata lists 3.7 and 3.8. Validate against the vendor advisory before closing exposure.

Mitigation direction

  • Follow the VMware Tanzu advisory for supported fixed versions.
  • Upgrade RabbitMQ 3.8.x installations to 3.8.7 or later where applicable.
  • Restrict write access to the RabbitMQ installation directory.
  • Review service account privileges on Windows RabbitMQ hosts.
  • Remove unnecessary local access to RabbitMQ servers.

Validation and detection

  • Inventory Windows hosts running RabbitMQ 3.7 or 3.8.
  • Confirm exact RabbitMQ version and compare against vendor guidance.
  • Audit RabbitMQ installation directory ACLs for unexpected write access.
  • Review local users and service accounts with server access.
  • Check for unauthorized files in the installation directory.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-427: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-5419 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.7 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.7CVSS 3.0MediumCVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H0.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

6.7Medium
CVSS 3.0 vector shape for CVE-2020-5419Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
VMware TanzuRabbitMQ3.7, 3.8Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-427 · source CWE mapping

Uncontrolled Search Path Element

Uncontrolled Search Path Element represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.