aMQTT: Denial of Service (DoS) via Memory Leak in Unmanaged QoS 2 Session Handshakes
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Yakifo | amqtt | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Yakifo | Amqtt |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-wcqj-wx85-c75p | aMQTT: Denial of Service (DoS) via Memory Leak in Unmanaged QoS 2 Session Handshakes |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.623% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Yakifo
Yakifo amqtt |
|
| Vendors & Products |
Yakifo
Yakifo amqtt |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | aMQTT is an open source MQTT broker and client. From 0.11.0 until 0.12.1, the QoS 2 transaction handler in amqtt/mqtt/protocol/handler.py, _handle_qos2_message_flow(), can retain transaction state and packet identifiers when a client disconnects before the handshake completes, unlike QoS 1 flows that expire after the default five-second timeout. A remote client can repeatedly begin QoS 2 flows and disconnect without maintaining long-lived connections; anonymous clients can do this with the default configuration, while authenticated deployments remain affected when a client may initiate QoS 2 flows. The retained state grows broker memory until resource exhaustion can terminate the process; no confidentiality or integrity impact is identified. This issue is fixed in version 0.12.1. | |
| Title | aMQTT: Denial of Service (DoS) via Memory Leak in Unmanaged QoS 2 Session Handshakes | |
| Weaknesses | CWE-401 CWE-772 |
|
| References |
|
|
| Metrics |
cvssV3_1
|