Pivotal Software RabbitMQ 1.15.2 for Pivotal Cloud Foundry

CPE Details

Pivotal Software RabbitMQ 1.15.2 for Pivotal Cloud Foundry
pivotal_software
rabbitmq
1.15.2
2019-12-03
12h15 +00:00
2019-12-03
12h15 +00:00
CPE NVD
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:pivotal_software:rabbitmq:1.15.2:*:*:*:*:pivotal_cloud_foundry:*:*

Informations

Vendor

pivotal_software

Product

rabbitmq

Version

1.15.2

Target Software

pivotal_cloud_foundry

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2020-5419 2020-08-31 15h05 +00:00 RabbitMQ versions 3.8.x prior to 3.8.7 are prone to a Windows-specific binary planting security vulnerability that allows for arbitrary code execution. An attacker with write privileges to the RabbitMQ installation directory and local access on Windows could carry out a local binary hijacking (planting) attack and execute arbitrary code.
6.7
Medium
CVE-2019-11281 2019-10-16 15h23 +00:00 Pivotal RabbitMQ, versions prior to v3.7.18, and RabbitMQ for PCF, versions 1.15.x prior to 1.15.13, versions 1.16.x prior to 1.16.6, and versions 1.17.x prior to 1.17.3, contain two components, the virtual host limits page, and the federation management UI, which do not properly sanitize user input. A remote authenticated malicious user with administrative access could craft a cross site scripting attack that would gain access to virtual hosts and policy management information.
4.8
Medium
CVE-2018-1279 2018-12-10 19h00 +00:00 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.
8.5
High
CVE-2014-9494 2015-01-20 14h00 +00:00 RabbitMQ before 3.4.0 allows remote attackers to bypass the loopback_users restriction via a crafted X-Forwareded-For header.
5