Apache Qpid Broker-J: Unable to govern the maximum number of transfer frames per incoming delivery
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 | unaffected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Apache | Qpid Broker-j |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.653% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apache
Apache qpid Broker-j |
|
| Vendors & Products |
Apache
Apache qpid Broker-j |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | It was not possible to govern the maximum number of transfer frames per incoming delivery, enabling an authenticated attacker to cause excessive resource usage and potential denial of service. This issue affects Apache Qpid Broker-J: through 10.0.1. Users are recommended to upgrade to version 10.1.0, which fixes the issue. | |
| Title | Apache Qpid Broker-J: Unable to govern the maximum number of transfer frames per incoming delivery | |
| Weaknesses | CWE-770 | |
| References |
|