CVE-2016-9877

UnknownEPSS 1.38%

Last modified

CVE-2016-9877 is a vulnerability of currently unknown severity. 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. EPSS estimates a 1.38% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
1.38%

68.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
BroadcomRabbitmq Server3.0.0
BroadcomRabbitmq Server3.0.1
BroadcomRabbitmq Server3.0.2
BroadcomRabbitmq Server3.0.3
BroadcomRabbitmq Server3.0.4
BroadcomRabbitmq Server3.1.0
BroadcomRabbitmq Server3.1.1
BroadcomRabbitmq Server3.1.2
BroadcomRabbitmq Server3.1.3
BroadcomRabbitmq Server3.1.4
BroadcomRabbitmq Server3.1.5
BroadcomRabbitmq Server3.2.0
BroadcomRabbitmq Server3.2.1
BroadcomRabbitmq Server3.2.2
BroadcomRabbitmq Server3.2.3
BroadcomRabbitmq Server3.2.4
BroadcomRabbitmq Server3.3.0
BroadcomRabbitmq Server3.3.1
BroadcomRabbitmq Server3.3.2
BroadcomRabbitmq Server3.3.3
BroadcomRabbitmq Server3.3.4
BroadcomRabbitmq Server3.3.5
BroadcomRabbitmq Server3.4.0
BroadcomRabbitmq Server3.4.1
BroadcomRabbitmq Server3.4.2
BroadcomRabbitmq Server3.4.3
BroadcomRabbitmq Server3.4.4
BroadcomRabbitmq Server3.5.0
BroadcomRabbitmq Server3.5.1
BroadcomRabbitmq Server3.5.2
BroadcomRabbitmq Server3.5.3
BroadcomRabbitmq Server3.5.6
Pivotal SoftwareRabbitmq3.5.4
Pivotal SoftwareRabbitmq3.5.5
Pivotal SoftwareRabbitmq3.5.7
Pivotal SoftwareRabbitmq3.6.0
Pivotal SoftwareRabbitmq3.6.1
Pivotal SoftwareRabbitmq3.6.2
Pivotal SoftwareRabbitmq3.6.3
Pivotal SoftwareRabbitmq3.6.4
Pivotal SoftwareRabbitmq3.6.5
Pivotal SoftwareRabbitmq1.5.0
Pivotal SoftwareRabbitmq1.5.1
Pivotal SoftwareRabbitmq1.5.2
Pivotal SoftwareRabbitmq1.5.3
Pivotal SoftwareRabbitmq1.5.4
Pivotal SoftwareRabbitmq1.5.5
Pivotal SoftwareRabbitmq1.5.6
Pivotal SoftwareRabbitmq1.5.7
Pivotal SoftwareRabbitmq1.5.8

Showing 50 of 76 affected configurations. See NVD for the full list.

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-9877?
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.
How severe is CVE-2016-9877?
Severity scoring for CVE-2016-9877 is pending analysis. The EPSS model estimates a 1.38% probability of exploitation in the next 30 days.
How do I fix CVE-2016-9877?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-9877?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST