Qpid Broker JApplication · Apache
CVE-2019-0200
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 · uneditedA 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.
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 confidenceA Denial of Service vulnerability in Apache Qpid Broker-J versions 6.0.0-7.0.6 and 7.1.0 allows unauthenticated attackers to crash the broker by sending specially crafted commands via AMQP protocols 0-8, 0-9, 0-91, and 0-10 (versions below 1.0).
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.0, <= 7.0.6= 7.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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 installed Qpid Broker-J versionCheck the broker startup logs, management interface, or inspect the qpid-boot*.jar file name in the installation directory for the version numberAffected if Version is 6.0.0 through 7.0.6 inclusive, or exactly 7.1.0
-
Verify AMQP protocol bindings in broker configurationOpen the broker configuration XML file (typically in etc/config.xml or etc/broker.xml) and search for acceptor or protocol binding definitions; look for references to 'amqp0-8', 'amqp0-9', 'amqp0-91', or 'amqp0-10'Affected if Any acceptor is configured to accept AMQP protocol versions 0-8, 0-9, 0-91, or 0-10
-
Check open ports for legacy AMQP listenersRun 'netstat -an' or 'ss -an' on the broker host and look for ports configured to accept the legacy AMQP protocols; cross-reference with the configuration from step 2Affected if The broker is listening on ports configured for AMQP protocols below 1.0 (versions 0-8, 0-9, 0-91, or 0-10)
A broker is vulnerable if it runs version 6.0.0-7.0.6 or 7.1.0 AND has any AMQP protocol 0-8, 0-9, 0-91, or 0-10 acceptor enabled and reachable.
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 to Qpid Broker-J version 7.0.7 or 7.1.1 or later; alternatively, disable AMQP protocols below 1.0 if immediate upgrade is not feasible.
Fix this in Qpid Broker J
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing4.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0200 — 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-2019-0200 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