CVE intelligence and bounded remediation

CVE-2016-8741 — The Apache Qpid Broker for Java can be configured to use different so called AuthenticationProviders to handle user authentication

High CVSS 7.5

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.

Severity
High
CVSS
7.5 (3.1)
Published
2017-05-15
CISA KEV
Not currently listed
Ecosystem
java/maven
Weaknesses
CWE-200

Affected products

  • apache / qpid_broker-j / 6.0.1
  • apache / qpid_broker-j / 6.0.2
  • apache / qpid_broker-j / 6.0.3
  • apache / qpid_broker-j / 6.0.4
  • apache / qpid_broker-j / 6.0.5
  • apache / qpid_broker-j / 6.1.0

Matched remediation archetype

Information disclosure and sensitive data exposure

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Trace sensitive data through responses, errors, logs, metrics, traces, caches, exports, files, backups, and client bundles.
  • Identify affected subjects, tenants, retention windows, access controls, and downstream copies without opening unnecessary sensitive records.
  • Review metadata, timing, status, length, and existence signals as well as direct content disclosure.

Remediate safely

  • Minimize collection and output, apply field-level authorization and redaction at a centralized boundary, and return generic external errors.
  • Remove secrets and sensitive data from logs, artifacts, URLs, caches, and client-side bundles; rotate credentials that may have been exposed.
  • Update the affected component and add synthetic-data tests for response, error, observability, and export paths.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.