An issue was discovered in Pivotal RabbitMQ 3.x before 3.5.8 and 3.6.x before 3.6.6 and RabbitMQ for PCF 1.5.x before 1.5.20, 1.6.x before 1.6.12, and 1.7.x before 1.7.7. MQTT (MQ Telemetry Transport) connection authentication with a username/password pair succeeds if an existing username is provided but the password is omitted from the connection request. Connections that use TLS with a client-provided certificate are not affected.

Pivotal.io reports :

All versions prior to 3.8.16 are prone to a denial of service vulnerability due to improper input validation in AMQP 1.0 client connection endpoint.

It was discovered that RabbitMQ incorrectly handled MQTT (MQ Telemetry Transport) authentication. A remote attacker could use this issue to authenticate successfully with an existing username by omitting the password.

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

- Fix 0.0.0 as a version.

----

  - Ver. 3.6.6

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

This update for rabbitmq-server fixes the following issue :

  - CVE-2016-9877: An issue in Pivotal RabbitMQ caused     connection authentication with a username/password pair     to succeed if an existing username was provided but the     password is omitted from the connection request.
    Connections that use TLS with a client-provided     certificate were not affected (bsc#1017642).

Pivotal.io reports :

MQTT (MQ Telemetry Transport) connection authentication with a username/password pair succeeds if an existing username is provided but the password is omitted from the connection request. Connections that use TLS with a client-provided certificate are not affected.

It was discovered that RabbitMQ, an implementation of the AMQP protocol, didn't correctly validate MQTT (MQ Telemetry Transport) connection authentication. This allowed anyone to login to an existing user account without having to provide a password.

ID	Name	Product	Family	Severity
152207	FreeBSD : RabbitMQ -- Denial of Service in AMQP1.0 plugin (b1aa54ae-74cb-42a0-b462-cbb6831c5c50)	Nessus	FreeBSD Local Security Checks	critical
102093	Ubuntu 14.04 LTS / 16.04 LTS : RabbitMQ vulnerability (USN-3374-1)	Nessus	Ubuntu Local Security Checks	critical
97805	Fedora 25 : rabbitmq-server (2017-534e23bad9)	Nessus	Fedora Local Security Checks	critical
96864	openSUSE Security Update : rabbitmq-server (openSUSE-2017-156)	Nessus	SuSE Local Security Checks	critical
96512	FreeBSD : RabbitMQ -- Authentication vulnerability (6aa956fb-d97f-11e6-a071-001e67f15f5a)	Nessus	FreeBSD Local Security Checks	critical
96494	Debian DSA-3761-1 : rabbitmq-server - security update	Nessus	Debian Local Security Checks	critical

Detections

Analytics

CVE-2016-9877

critical

Tenable Plugins

critical

critical

critical

critical

critical

critical