# CVE-2020-5419: RabbitMQ arbitrary code execution using local binary planting

> Local attackers with write access to the installation directory can execute arbitrary code via binary planting on Windows.

- **Severity:** Medium 6.7 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Aug 2020
- **Updated:** 16 Sep 2024
- **Also known as:** BIT-rabbitmq-2020-5419, GHSA-82gq-g626-8g5r

## What is CVE-2020-5419?

CVE-2020-5419 is a medium-severity code injection vulnerability in Broadcom Rabbitmq Server, published on 31 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2020-5419?

1 open source package ship an affected version, including rabbitmq. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rabbitmq` | Bitnami | From 3.8.0 | 3.8.7 |

Products: Broadcom Rabbitmq Server, Pivotal Software Rabbitmq.

## How do I fix CVE-2020-5419?

Upgrade rabbitmq to 3.8.7 or later.

## Is CVE-2020-5419 being exploited?

There is no known exploitation of CVE-2020-5419 in the wild and no public exploit code.

## Other vulnerabilities in Broadcom Rabbitmq Server

- [CVE-2016-9877](https://insights.sbomify.com/CVE-2016-9877/): Auth bypass in Pivotal RabbitMQ 3.x before 3.5.8 and 3.6.x before 3.6.6; RabbitMQ for PCF 1.5.x before 1.5.20, 1.6.x before 1.6.12 and 1.7.x before 1.7.7 (critical 9.8)
- [CVE-2026-67404](https://insights.sbomify.com/CVE-2026-67404/): RabbitMQ: OAuth2 silent verify_none fallback for JWKS fetch (critical 9.2)
- [CVE-2026-67231](https://insights.sbomify.com/CVE-2026-67231/): RabbitMQ: Trust-store whitelist by Issuer+Serial only (critical 9.1)
- [CVE-2026-57219](https://insights.sbomify.com/CVE-2026-57219/): Information disclosure in rabbitmq-server (high 8.7)
- [CVE-2026-67236](https://insights.sbomify.com/CVE-2026-67236/): RabbitMQ: Plaintext username:password stored in an insecure cookie after successful POST /login (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-5419 and fix it if it is affected.

What it is: CVE-2020-5419 is a medium-severity code injection vulnerability in Broadcom Rabbitmq Server, published on 31 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-5419 in the wild and no public exploit code.

Affected packages and fixed versions:
- rabbitmq (Bitnami): affected from 3.8.0; fixed in 3.8.7

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-5419/ (Markdown: https://insights.sbomify.com/CVE-2020-5419/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-5419
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-5419
- OSV: https://osv.dev/vulnerability/CVE-2020-5419

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-5419/
Summaries are generated and may contain mistakes; the official description above is the record.