cve.bz

CVE-2018-1279 pivotal software rabbitmq: Use of Insufficiently Random Values

6.5 mediumEPSS 1.8%

Medium (6.5) in pivotal software rabbitmq. EPSS 1.8% estimated probability of exploitation activity in the next 30 days.

On this page
Pivotal RabbitMQ for PCF, all versions, uses a deterministically generated cookie that is shared between all machines when configured in a multi-tenant cluster. A remote attacker who can gain information about the network topology can guess this cookie and, if they have access to the right ports on any server in the MQ cluster can use this cookie to gain full control over the entire cluster.

Severity

CVSS 3.0

6.5 medium
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
1.8% (unchanged from 1.8% a week ago; 1.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 79th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-330 Use of Insufficiently Random Values
OWASP Top 10
A04:2025 Cryptographic Failures
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-2018-1279 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2018-1279?via=ask-ai-copy and https://cve.bz/cve/CVE-2018-1279?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-2018-1279 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 CNA's record in the CVE List.

ProductAffected
Pivotal RabbitMq for PCFfrom 1 before all versions*

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14rabbitmq-server3.9.8-5DEBIAN-CVE-2018-1279
UbuntuPro:16.04:LTS, Pro:18.04:LTS, Pro:20.04:LTSrabbitmq-serverno fix listedUBUNTU-CVE-2018-1279

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 Important.

Red Hat's statement

OpenShift Online:

RabbitMQ is only used by the Ansible Tower, which is not a standard part of the OpenShift product, however is deployed as a management tool.

This is set as deferred as it has no impact to customers and is not deployed in a clustered configuration. A cluster using an Erlang-generated cookie would be required for cookie guessing to provide and environmental leverage.

OpenStack:

For RHOSP10+, the rabbit cookie is set to a random string during deployment, rather than relying on Erlang to generate the cookie, if the cookie has not been overridden in the deployment configuration. In either case, this avoids the predictable Erlang cookie generation highlighted by this flaw, meaning RHOSP10+ is not vulnerable. Further mitigating the flaw, is the fact that RabbitMQ, in an OpenStack context, is deployed to the admin network and as such should only be accessible to OpenStack services, not public users via an external network.

For RHOSP8+9, when deployed with Director (TripleO), the RabbitMQ salt is initialized via the Heat RandomString function, also bypassing this vulnerability. RHOSP8+9 however did not use Director as the default deployment mechanism. When installing RHOSP manually in these versions, our installation documentation does not provide guidance for configuring clustered RabbitMQ. It is safe to assume that some customers may have this configured in an insecure way, despite the fact that we would not have told them how to install and configure a cluster in a vulnerable way.

Ansible Tower:

In Tower we do not use the programmatic cookie generation that gives rise to this vulnerability. Instead we use cookiemonster. So this issue does not affect Ansible Tower.

CloudForms (CFME):

RabbitMQ shipped with CloudForms is exclusively used by Ansible Tower. Since Ansible Tower is not vulnerable, due to the reasons described above, then CloudForms isn't, as well.

ProductPackageStateAdvisory
CloudForms Management Engine 5rabbitmq-serverNot affected
Red Hat Ansible Tower 3rabbitmq-serverNot affected
Red Hat OpenStack Platform 10 (Newton)rabbitmq-serverOut of support scope
Red Hat OpenStack Platform 13 (Queens)rabbitmq-serverWill not fix
Red Hat OpenStack Platform 14 (Rocky)rabbitmq-serverOut of support scope
Red Hat OpenStack Platform 8 (Liberty)rabbitmq-serverOut of support scope
Red Hat OpenStack Platform 9 (Mitaka)rabbitmq-serverOut of support scope

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-2018-1279.

Attack patterns (CAPEC)

  • CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
  • CAPEC-112 Brute Force Severity: High
  • CAPEC-485 Signature Spoofing by Key Recreation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON