Qpid Broker JApplication · Apache
CVE-2018-8030
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 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.
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 confidenceApache Qpid Broker-J versions 7.0.0-7.0.4 crashes when AMQP protocols 0-8, 0-9, or 0-91 are used to publish messages exceeding the 100MB default size limit, causing a Denial of Service. Protocols 0-10 and 1.0 are unaffected.
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
>= 7.0.0, <= 7.0.4CVSS 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.
-
Determine installed Qpid Broker-J versionCheck the broker's version through the management web console (typically at port 8080 or 8443), or inspect the broker's startup logs, or run 'qpid-server --version' if the command line tools are available, or check the lib/qpid-boot*.jar file nameAffected if The version is 7.0.0, 7.0.1, 7.0.2, 7.0.3, or 7.0.4
-
Identify active AMQP protocol versionsReview the broker configuration files (typically in etc/ or config/ directory) for AMQP connector settings, or check the management console for active connections and their protocol versions, or inspect the broker logs for connection protocol headersAffected if The broker is accepting or has accepted connections using AMQP protocols 0-8, 0-9, or 0-91 (these protocols are in use)
-
Verify message size limit configurationInspect the broker configuration for 'maxMessageSize' or 'maximumMessageSize' settings in the AMQP port configuration (often in the connection URL or profile settings), or check the management console for message size limitsAffected if The message size limit is unset or set to a value of 104857600 bytes (100MB) or higher, or the default is in effect
You are affected if your Qpid Broker-J version is between 7.0.0 and 7.0.4 inclusive, AND you have AMQP protocols 0-8, 0-9, or 0-91 enabled/active, AND your message size limit allows messages larger than 100MB (default or explicit).
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 a patched version of Qpid Broker-J (7.0.5 or later), or implement message size validation/proxy-level filtering before messages reach the broker, or migrate to AMQP 0-10 or 1.0 protocols.
Fix this in Qpid Broker J
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-8030 — 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-2018-8030 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