Skip to content

Exposure of Sensitive Information to an Unauthorized Actor in Apache Qpid Broker for Java

High severity GitHub Reviewed Published May 17, 2022 to the GitHub Advisory Database • Updated May 22, 2023

Package

maven org.apache.qpid:qpid-broker (Maven)

Affected versions

>= 6.0.0, <= 6.0.5
= 6.1.0

Patched versions

6.0.6
6.1.1

Description

The Apache Qpid Broker for Java can be configured to use different so called AuthenticationProviders to handle user authentication. Among the choices are the SCRAM-SHA-1 and SCRAM-SHA-256 AuthenticationProvider types. It was discovered that these AuthenticationProviders in Apache Qpid Broker for Java 6.0.x before 6.0.6 and 6.1.x before 6.1.1 prematurely terminate the SCRAM SASL negotiation if the provided user name does not exist thus allowing remote attacker to determine the existence of user accounts. The Vulnerability does not apply to AuthenticationProviders other than SCRAM-SHA-1 and SCRAM-SHA-256.

References

Published by the National Vulnerability Database May 15, 2017
Published to the GitHub Advisory Database May 17, 2022
Reviewed Jul 6, 2022
Last updated May 22, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.125%
(48th percentile)

Weaknesses

CVE ID

CVE-2016-8741

GHSA ID

GHSA-8vvh-crqv-jm64

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.