Skip to content
Fencer Intel
high 7.3

CVE-2015-5329 json

The TripleO Heat templates (tripleo-heat-templates), as used in Red Hat Enterprise Linux OpenStack Platform 7.0, do not properly use the co…

published 2016-04-11 10 y ago modified 2026-06-17 4 mo ago also EUVD-2015-5300

cvss
7.3
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits
0
none known

Summary

The TripleO Heat templates (tripleo-heat-templates), as used in Red Hat Enterprise Linux OpenStack Platform 7.0, do not properly use the configured RabbitMQ credentials, which makes it easier for remote attackers to obtain access to services in deployed overclouds by leveraging knowledge of the default credentials.

Patch / fix

  • python-rdomanager-oscplugin openstack-director 7 0.0.10-22.el7ost
  • openstack-tripleo-heat-templates openstack-director 7 0.8.6-94.el7ost

red hat advisories RHSA-2015:2650

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-5329 updated cvss 5.8

openstack-tripleo-heat-templates: Using hardcoded rabbitmq credentials regardless of supplied values

  • Red Hat Enterprise Linux OpenStack Platform 6 (Juno) openstack-tripleo-heat-templates
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack 7.0 Director for RHEL 7 python-rdomanager-oscplugin 0.0.10-22.el7ost, openstack-tripleo-heat-templates 0.8.6-94.el7ost
    fixed: vendor fix RHSA-2015:2650

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.52% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.