Qpid Broker JApplication · Apache
CVE-2016-8741
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe SCRAM-SHA-1 and SCRAM-SHA-256 AuthenticationProviders in Apache Qpid Broker for Java versions 6.0.x before 6.0.6 and 6.1.x before 6.1.1 prematurely terminate the SCRAM SASL negotiation when an invalid username is provided, allowing remote attackers to enumerate valid user accounts by observing the different error responses.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Qpid Broker JApplication
= 6.0.1= 6.0.2= 6.0.3= 6.0.4= 6.0.5= 6.1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Qpid Broker for Java installationLocate the Qpid Broker J process or installation directory. Check for qpid broker JAR files or running Java process with 'qpid' in the command line.Affected if Apache Qpid Broker for Java is present in the environment
-
Determine the installed versionInspect the broker's version information, typically found in the broker JAR filename, MANIFEST.MF file, or broker logs at startup.Affected if Version is 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, or 6.1.0
-
Identify enabled AuthenticationProvidersReview the broker configuration file (typically qpid-config.json or authentication-providers.xml) to list configured AuthenticationProvider types.Affected if SCRAM-SHA-1 or SCRAM-SHA-256 AuthenticationProvider is enabled in the configuration
-
Assess network accessibilityDetermine if the broker's AMQP port (default 5672) is exposed to untrusted networks or directly to the internet.Affected if Broker port is accessible from untrusted network sources
Environment is affected if running a vulnerable Qpid Broker J version (6.0.1-6.0.5 or 6.1.0) with SCRAM-SHA-1 or SCRAM-SHA-256 AuthenticationProvider enabled and accessible to remote attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Apache Qpid Broker for Java to version 6.0.6, 6.1.1, or later; alternatively, switch to a non-SCRAM AuthenticationProvider if upgrade is not feasible.
Fix this in Qpid Broker J
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-8741 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-8741 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data