Approved changes feed: RSS · Atom

cpe:2.3:a:apache:qpid_broker-j:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorApache (b0303047-b7dd-5cf8-abcc-71b7d9d80b95)
ProductQpid Broker J (f856a025-75ee-5353-a01d-f4b458868a5f)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:apache/qpid purl2cpe 2026-06-01 10:14:31.527561
pkg:github/apache/qpid-broker-j purl2cpe 2026-06-01 10:14:31.527563
pkg:maven/org.apache.qpid/apache-qpid-broker-j purl2cpe 2026-06-01 10:14:31.527565

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2019-0200 vulnerable 2026-06-08 05:12:19.255711 Details available
A Denial of Service vulnerability was found in Apache Qpid Broker-J versions 6.0.0-7.0.6 (inclusive) and 7.1.0 which allows an unauthenticated attacker to crash the broker instance by sending specially crafted commands using AMQP protocol versions below 1.0 (AMQP 0-8, 0-9, 0-91 and 0-10). Users of Apache Qpid Broker-J versions 6.0.0-7.0.6 (inclusive) and 7.1.0 utilizing AMQP protocols 0-8, 0-9, 0-91, 0-10 must upgrade to Qpid Broker-J versions 7.0.7 or 7.1.1 or later.
Published: 2019-03-06T18:00:00.000Z
Updated: 2024-09-16T20:58:31.100Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2018-8030 vulnerable 2026-06-08 05:12:05.027613 Details available
A Denial of Service vulnerability was found in Apache Qpid Broker-J versions 7.0.0-7.0.4 when AMQP protocols 0-8, 0-9 or 0-91 are used to publish messages with size greater than allowed maximum message size limit (100MB by default). The broker crashes due to the defect. AMQP protocols 0-10 and 1.0 are not affected.
Published: 2018-06-19T13:00:00.000Z
Updated: 2024-09-16T19:41:52.432Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2017-15702 vulnerable 2026-06-08 05:08:59.410765 Details available
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 authentication provider that was configured on a different port. The attacker still needs valid credentials with the authentication provider on the spoofed port. This becomes an issue when the spoofed port has weaker authentication protection (e.g., anonymous access, default accounts) and is normally protected by firewall rules or similar which can be circumvented by this vulnerability. AMQP ports are not affected. Versions 6.0.0 and newer are not affected.
Published: 2017-12-01T15:00:00.000Z
Updated: 2024-09-16T16:38:43.290Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2017-15701 vulnerable 2026-06-08 05:08:59.410306 Details available
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 AMQP protocols are not affected.
Published: 2017-12-01T15:00:00.000Z
Updated: 2024-09-16T16:28:48.395Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2016-4432 vulnerable 2026-06-08 05:07:47.405028 Details available
The AMQP 0-8, 0-9, 0-91, and 0-10 connection handling in Apache Qpid Java before 6.0.3 might allow remote attackers to bypass authentication and consequently perform actions via vectors related to connection state logging.
Published: 2016-06-01T20:00:00.000Z
Updated: 2024-08-06T00:32:24.721Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2016-3094 vulnerable 2026-06-08 05:07:44.447440 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.