# CVE-2017-4966: Information disclosure in Pivotal RabbitMQ

> Attackers can retrieve stored user credentials from browser local storage in RabbitMQ management UI, potentially leading to account takeover.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-4966, GHSA-cp6g-c34h-69q7, UBUNTU-CVE-2017-4966, USN-6265-1

## What is CVE-2017-4966?

CVE-2017-4966 is a high-severity vulnerability in Broadcom Rabbitmq Server, published on 13 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in these Pivotal RabbitMQ versions: all 3.4.x versions, all 3.5.x versions, and 3.6.x versions prior to 3.6.9; and these RabbitMQ for PCF versions: all 1.5.x versions, 1.6.x versions prior to 1.6.18, and 1.7.x versions prior to 1.7.15. RabbitMQ management UI stores signed-in user credentials in a browser's local storage without expiration, making it possible to retrieve them using a chained attack.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-4966?

It affects 3 products.


Products: Broadcom Rabbitmq Server, Debian Debian Linux, Pivotal Software Rabbitmq.

## How do I fix CVE-2017-4966?

Upgrade to a fixed version.

## Is CVE-2017-4966 being exploited?

There is no known exploitation of CVE-2017-4966 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-2017-4966 and fix it if it is affected.

What it is: CVE-2017-4966 is a high-severity vulnerability in Broadcom Rabbitmq Server, published on 13 Jun 2017. 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-2017-4966 in the wild and no public exploit code.

Affected product: Broadcom Rabbitmq Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2017-4966/ (Markdown: https://insights.sbomify.com/CVE-2017-4966/index.md)
```

## Sources

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

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