CVE-2016-8741

qpid-java: Information leakage via specific AuthenticationProviders

Published May 15, 2017 CVSS 3.1 · 7.5 High EPSS 6.4% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2022-3246 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.
Github GHSA Github GHSA GHSA-8vvh-crqv-jm64 Exposure of Sensitive Information to an Unauthorized Actor in Apache Qpid Broker for Java
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Aug 6, 2024, 2:34 AM
Reserved
Oct 18, 2016, 12:00 AM
Status
Modified
Published
May 15, 2017, 2:29 PM
Modified
Jun 17, 2026, 12:54 AM
Severity
Low
Public date
Dec 28, 2016, 12:00 AM