tinyMQTT Broker Resource Exhaustion via Malformed CONNECT Packet
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Justdoit0910 | Tinymqtt |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.278% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Title | tinyMQTT Broker Resource Exhaustion via Malformed CONNECT Packet |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Open TCP Connection Leakage Causes Denial of Service in tinyMQTT via Malformed CONNECT | |
| Weaknesses | CWE-770 |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Justdoit0910
Justdoit0910 tinymqtt |
|
| Vendors & Products |
Justdoit0910
Justdoit0910 tinymqtt |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Open TCP Connection Leakage Causes Denial of Service in tinyMQTT via Malformed CONNECT | |
| Weaknesses | CWE-400 CWE-770 |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In tinyMQTT commit 6226ade15bd4f97be2d196352e64dd10937c1962 (2024-02-18), the broker mishandles protocol violations during CONNECT packet parsing. When receiving a CONNECT packet with a zero-length Client ID while CleanSession is set to 0, the broker correctly replies with a CONNACK return code 0x02 (Identifier Rejected) but fails to explicitly close the TCP connection. Since the surrounding connection teardown logic is not guaranteed to execute, each such invalid CONNECT attempt leaves the underlying socket open. Repeated attempts cause server-side resource exhaustion due to accumulating file descriptors and memory usage, potentially resulting in denial of service. | |
| References |
|