CVE-2015-5329

Description

A flaw was found in the director (openstack-tripleo-heat-templates) where the RabbitMQ credentials defaulted to guest/guest and supplied values in the configuration were not used. As a result, all deployed overclouds used the same credentials (guest/guest). A remote non-authenticated attacker could use this flaw to access RabbitMQ services in the deployed cloud.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v2 Score Breakdown

Red HatNVDcve.org
Base Score5.87.5N/A
Attack VectorAdjacent NetworkNetworkN/A
Access ComplexityLowLowN/A
AuthenticationNoneNoneN/A
Confidentiality ImpactPartialPartialN/A
Integrity ImpactPartialPartialN/A
Availability ImpactPartialPartialN/A

Vector

Red Hat: AV:A/AC:L/Au:N/C:P/I:P/A:P

NVD: AV:N/AC:L/Au:N/C:P/I:P/A:P

Understanding the Weakness (CWE)

Access Control

Technical Impact: Bypass Protection Mechanism

If hard-coded passwords are used, it is almost certain that malicious users will gain access to the account in question. Any user of the product that hard-codes passwords may be able to extract the password. Client-side systems with hard-coded passwords pose even more of a threat, since the extraction of a password from a binary is usually very simple.

Integrity,Confidentiality,Availability,Access Control,Other

Technical Impact: Read Application Data; Gain Privileges or Assume Identity; Execute Unauthorized Code or Commands; Other

This weakness can lead to the exposure of resources or functionality to unintended actors, possibly providing attackers with sensitive information or even execute arbitrary code. If the password is ever discovered or published (a common occurrence on the Internet), then anybody with knowledge of this password can access the product. Finally, since all installations of the product will have the same password, even across different organizations, this enables massive attacks such as worms to take place.

Acknowledgements

Red Hat would like to thank Kota Akatsuka (NEC) for reporting this issue.

Frequently Asked Questions

Want to get errata notifications? Sign up here.