Apache Qpid Broker-J: Type size/count handling can lead to excessive allocation pre-authentication
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.774% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| 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 | A pre-authentication attacker could leverage type size/count handling to cause excessive allocation leading to 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: Type size/count handling can lead to excessive allocation pre-authentication | |
| Weaknesses | CWE-770 | |
| References |
|