Description
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.
Metrics
CVSS 3.1 7.5/10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| Apache Software Foundation | Apache Qpid Broker-J | 6.1.0, 6.1.1, 6.1.2, 6.1.3, and 6.1.4 |
References
- http://www.securityfocus.com/bid/102041Third Party Advisory, VDB Entry
- https://issues.apache.org/jira/browse/QPID-7947Issue Tracking, Vendor Advisory
- https://lists.apache.org/thread.html/4054e1c90993f337eeea24a312841c0661653e673c0ff8e2cd9520fe%40%3Cdev.qpid.apache.org%3E
- https://qpid.apache.org/cves/CVE-2017-15701.htmlMitigation, Vendor Advisory
- http://www.securityfocus.com/bid/102041Third Party Advisory, VDB Entry
- https://issues.apache.org/jira/browse/QPID-7947Issue Tracking, Vendor Advisory
- https://lists.apache.org/thread.html/4054e1c90993f337eeea24a312841c0661653e673c0ff8e2cd9520fe%40%3Cdev.qpid.apache.org%3E
- https://qpid.apache.org/cves/CVE-2017-15701.htmlMitigation, Vendor Advisory
Timeline
- Published
- Dec 1, 2017
- Last modified
- Jun 17, 2026
- NVD status
- Modified