Qpid Broker JApplication · Apache
CVE-2017-15701
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 · uneditedIn 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.
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 6.1.0-6.1.4 lack proper validation of maximum frame size in AMQP 1.0 protocol frames. A remote unauthenticated attacker can send oversized frames that cause unbounded memory allocation, leading to memory exhaustion and broker termination.
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.1.0, <= 6.1.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.1/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 Qpid Broker-J versionLocate the Qpid Broker-J installation and determine its version number. Check the broker's startup logs, the version.properties file in the installation directory, or query the broker's management interface if available.Affected if Installed version is 6.1.0, 6.1.1, 6.1.2, 6.1.3, or 6.1.4
-
Confirm AMQP 1.0 protocol is enabledInspect the broker configuration files for AMQP 1.0 transport acceptors or connectors. Look for AMQP 1.0 ports or bindings in the broker's XML configuration (commonly qpid-config.xml or similar).Affected if AMQP 1.0 protocol support is enabled and accessible over the network
-
Check for frame size validation settingsExamine the AMQP 1.0 transport configuration for any maximum frame size parameters. Look for attributes like frameSize, maximumFrameSize, or similar in the transport configuration section of the broker's XML config files.Affected if No maximum frame size limit is configured or the configured limit allows arbitrarily large frames
-
Verify connection and memory limits existReview the broker's resource management settings for connection limits, memory thresholds, or flow control mechanisms. Check the broker config for any pooling, throttling, or resource quota settings.Affected if No effective connection limits or memory protections are configured to mitigate unbounded memory allocation
You are affected if the broker runs a version between 6.1.0 and 6.1.4 inclusive AND has AMQP 1.0 protocol enabled without proper frame size validation.
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 6.1.5 or later which addresses this vulnerability. Alternatively, implement network-level frame size filtering or connection limits as a compensating control.
Fix this in Qpid Broker J
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15701 — 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-2017-15701 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