LiveActive security incident?Get immediate response
CVE Record

CVE-2016-8741: The Apache Qpid Broker for Java can be configured to use different so called AuthenticationProviders to han...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This flaw can let a remote attacker learn whether specific usernames exist on affected Apache Qpid Broker-J systems. It is not described as remote code execution or direct credential theft, but account enumeration can make later phishing, password guessing, or targeted attacks easier. Exposure is likely limited to organizations running affected Apache Qpid Broker-J versions with SCRAM-SHA-1 or SCRAM-SHA-256 AuthenticationProviders reachable by untrusted users or networks. Treat as a targeted hardening item rather than an emergency. Prioritize internet-facing or partner-facing brokers first because username disclosure can support follow-on attacks. Mitigation focus: Upgrade Apache Qpid Broker-J to 6.0.6, 6.1.1, or a later supported release.; Review Apache Qpid vendor guidance and QPID-7599 for release-specific remediation details.; If upgrade is delayed, restrict broker authentication access to trusted networks..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-8741 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache Qpid Broker-J6.0.1, 6.0.2, 6.0.3, 6.0.4, and 6.0.5, 6.1.0Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.