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
Published Dec 1, 2017
7.5
HIGHCVSS 3.1
EPSS 4.39%
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.
Affected products
-
- Version 6.1.0, 6.1.1, 6.1.2, 6.1.3, and 6.1.4StatusaffectedConstraints-
- Version
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Apache Software Foundation | Apache Qpid Broker-J | n/a |
|
- ≥ 6.1.0 · ≤ 6.1.4
No data.
No Red Hat product state for this CVE.
No package ranges for this CVE.
Remediation
No remediation recorded yet.
Metrics
No CVSS v4.0 score for this CVE.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
No CVSS v3.0 score for this CVE.
AV:N/AC:L/Au:N/C:N/I:N/A:P
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 1, 2026.
Score over time
2021–2026- EPSS v1
- EPSS v5
- EPSS v2
- EPSS v3
- EPSS v4
Percentile over time
- EPSS v1
- EPSS v5
- EPSS v2
- EPSS v3
- EPSS v4
Table of values (15 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 1, 2026 | 4.39% (0.04389) | 91.00th | v5 (v2026.06.15) |
| Jun 15, 2026 | 4.39% (0.04389) | 90.02th | v5 (v2026.06.15) |
| Mar 30, 2025 | 3.06% (0.03060) | 85.50th | v4 (v2025.03.14) |
| Mar 29, 2025 | 5.50% (0.05505) | 83.33th | v4 (v2025.03.14) |
| Mar 17, 2025 | 3.06% (0.03060) | 85.80th | v4 (v2025.03.14) |
| Dec 12, 2024 | 0.55% (0.00554) | 78.33th | v3 (v2023.03.01) |
| Jul 3, 2024 | 0.55% (0.00554) | 77.70th | v3 (v2023.03.01) |
| Feb 8, 2024 | 0.46% (0.00455) | 74.48th | v3 (v2023.03.01) |
| Sep 16, 2023 | 0.46% (0.00455) | 72.25th | v3 (v2023.03.01) |
| Sep 3, 2023 | 0.63% (0.00630) | 76.39th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.46% (0.00460) | 71.46th | v3 (v2023.03.01) |
| Mar 6, 2023 | 1.48% (0.01484) | 73.53th | v2 (v2022.01.01) |
| Feb 4, 2022 | 1.48% (0.01484) | 50.61th | v2 (v2022.01.01) |
| Feb 3, 2022 | 3.83% (0.03828) | 72.38th | v5 (v2026.06.15) |
| Apr 14, 2021 | 3.83% (0.03828) | 0.00th | v1 |
References (7)
- http://www.securityfocus.com/bid/102041 vdb-entryx_refsource_BIDThird Party AdvisoryVDB Entry
- https://github.com/advisories/GHSA-4r7g-7cpj-5jr7 Advisory
- https://issues.apache.org/jira/browse/QPID-7947 x_refsource_CONFIRMIssue TrackingVendor Advisory
- https://lists.apache.org/thread.html/4054e1c90993f337eeea24a312841c0661653e673c0ff8e2cd9520fe%40%3Cdev.qpid.apache.org%3E mailing-listx_refsource_MLIST
- https://lists.apache.org/thread.html/4054e1c90993f337eeea24a312841c0661653e673c0ff8e2cd9520fe@%3Cdev.qpid.apache.org%3E
- https://nvd.nist.gov/vuln/detail/CVE-2017-15701
- https://qpid.apache.org/cves/CVE-2017-15701.html x_refsource_CONFIRMMitigationVendor Advisory
| Link | Providers | Tags |
|---|---|---|
| http://www.securityfocus.com/bid/102041 | vdb-entryx_refsource_BIDThird Party AdvisoryVDB Entry | |
| https://github.com/advisories/GHSA-4r7g-7cpj-5jr7 | Advisory | |
| https://issues.apache.org/jira/browse/QPID-7947 | x_refsource_CONFIRMIssue TrackingVendor Advisory | |
| https://lists.apache.org/thread.html/4054e1c90993f337eeea24a312841c0661653e673c0ff8e2cd9520fe%40%3Cdev.qpid.apache.org%3E | mailing-listx_refsource_MLIST | |
| https://lists.apache.org/thread.html/4054e1c90993f337eeea24a312841c0661653e673c0ff8e2cd9520fe@%3Cdev.qpid.apache.org%3E | ||
| https://nvd.nist.gov/vuln/detail/CVE-2017-15701 | ||
| https://qpid.apache.org/cves/CVE-2017-15701.html | x_refsource_CONFIRMMitigationVendor Advisory |
Change history (0)
No recorded changes yet.