cve.bz

CVE-2017-4966

7.8 highEPSS 0.4%

High (7.8). EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2017-4966 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-4966?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-4966?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-4966 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
broadcom:rabbitmq_server3.4.0
broadcom:rabbitmq_server3.4.1
broadcom:rabbitmq_server3.4.2
broadcom:rabbitmq_server3.4.3
broadcom:rabbitmq_server3.4.4
broadcom:rabbitmq_server3.5.0
broadcom:rabbitmq_server3.5.1
broadcom:rabbitmq_server3.5.2
broadcom:rabbitmq_server3.5.3
broadcom:rabbitmq_server3.5.6
broadcom:rabbitmq_server3.6.7
pivotal_software:rabbitmq3.5.4
pivotal_software:rabbitmq3.5.5
pivotal_software:rabbitmq3.5.7
pivotal_software:rabbitmq3.6.0
pivotal_software:rabbitmq3.6.1
pivotal_software:rabbitmq3.6.2
pivotal_software:rabbitmq3.6.3
pivotal_software:rabbitmq3.6.4
pivotal_software:rabbitmq3.6.5
pivotal_software:rabbitmq3.6.6
pivotal_software:rabbitmq1.5.0
pivotal_software:rabbitmq1.5.1
pivotal_software:rabbitmq1.5.2
pivotal_software:rabbitmq1.5.3
pivotal_software:rabbitmq1.5.4
pivotal_software:rabbitmq1.5.5
pivotal_software:rabbitmq1.5.6
pivotal_software:rabbitmq1.5.7
pivotal_software:rabbitmq1.5.8
pivotal_software:rabbitmq1.5.9
pivotal_software:rabbitmq1.5.10
pivotal_software:rabbitmq1.5.11
pivotal_software:rabbitmq1.5.12
pivotal_software:rabbitmq1.5.13
pivotal_software:rabbitmq1.5.14
pivotal_software:rabbitmq1.5.15
pivotal_software:rabbitmq1.5.17
pivotal_software:rabbitmq1.5.18
pivotal_software:rabbitmq1.5.19
pivotal_software:rabbitmq1.6.0
pivotal_software:rabbitmq1.6.1
pivotal_software:rabbitmq1.6.2
pivotal_software:rabbitmq1.6.3
pivotal_software:rabbitmq1.6.4
pivotal_software:rabbitmq1.6.5
pivotal_software:rabbitmq1.6.6
pivotal_software:rabbitmq1.6.7
pivotal_software:rabbitmq1.6.8
pivotal_software:rabbitmq1.6.9
pivotal_software:rabbitmq1.6.10
pivotal_software:rabbitmq1.6.12
pivotal_software:rabbitmq1.6.13
pivotal_software:rabbitmq1.6.14
pivotal_software:rabbitmq1.6.15
pivotal_software:rabbitmq1.6.16
pivotal_software:rabbitmq1.7.0
pivotal_software:rabbitmq1.7.2
pivotal_software:rabbitmq1.7.3
pivotal_software:rabbitmq1.7.4
pivotal_software:rabbitmq1.7.5
pivotal_software:rabbitmq1.7.6
pivotal_software:rabbitmq1.7.7
pivotal_software:rabbitmq1.7.8
pivotal_software:rabbitmq1.7.9
pivotal_software:rabbitmq1.7.10
pivotal_software:rabbitmq1.7.13
pivotal_software:rabbitmq1.7.14
debian:debian_linux9.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian9rabbitmq-server3.6.6-1+deb9u1DLA-2710-1
Debian12, 13, 14rabbitmq-server3.6.10-1DEBIAN-CVE-2017-4966
UbuntuPro:16.04:LTSrabbitmq-server3.5.7-1ubuntu0.16.04.4+esm2UBUNTU-CVE-2017-4966 USN-6265-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This issue affects rabbitmq-server plugins as shipped with:

* Red Hat Storage Console 2

* Red Hat Enterprise Linux OpenStack Platform 5,6,7

* Red Hat OpenStack Platform 8,9,10,11

Although RabbitMQ plugins are shipped in these products, no plugins are enabled or used by default.

To verify your environment's plugin usage, run:

~~~

# rabbitmq-plugins list

~~~

A future update may address this issue. Red Hat Product Security has rated this issue as having Moderate security impact. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

ProductPackageStateAdvisory
Red Hat Enterprise Linux OpenStack Platform 5 (Icehouse)rabbitmq-serverWill not fix
Red Hat Enterprise Linux OpenStack Platform 6 (Juno)rabbitmq-serverWill not fix
Red Hat Enterprise Linux OpenStack Platform 7 (Kilo)rabbitmq-serverWill not fix
Red Hat OpenStack Platform 10 (Newton)rabbitmq-serverWill not fix
Red Hat OpenStack Platform 11 (Ocata)rabbitmq-serverWill not fix
Red Hat OpenStack Platform 8 (Liberty)rabbitmq-serverWill not fix
Red Hat OpenStack Platform 9 (Mitaka)rabbitmq-serverWill not fix
Red Hat Storage Console 2rabbitmq-serverWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2017-4966.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON