In Apache Qpid Broker-J 0.18 through 0.32, if the broker is configured with different authentication providers on different ports one of which is an HTTP port, then the broker can be tricked by a remote unauthenticated attacker connecting to the HTTP port into using an authentica...
Product
org.apache.qpid/qpid-broker vulnerabilities
4 published CVES affecting org.apache.qpid/qpid-broker, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 4
- Critical
- 1
- High
- 2
- Medium
- 1
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest org.apache.qpid/qpid-broker CVEs
Newest publication first
-
CriticalCVSS 9.8 EPSS 6.2%
-
HighCVSS 7.5 EPSS 4.4%
In Apache Qpid Broker-J versions 6.1.0 through 6.1.4 (inclusive) the broker does not properly enforce a maximum frame size in AMQP 1.0 frames. A remote unauthenticated attacker could exploit this to cause the broker to exhaust all available memory and eventually terminate. Older...
-
HighCVSS 7.5 EPSS 6.4%
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...
-
MediumCVSS 5.9 EPSS 7.8% Public exploit
PlainSaslServer.java in Apache Qpid Java before 6.0.3, when the broker is configured to allow plaintext passwords, allows remote attackers to cause a denial of service (broker termination) via a crafted authentication attempt, which triggers an uncaught exception.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.