Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionCVE.org
A segmentation fault in NanoMQ v0.21.10 allows attackers to cause a Denial of Service (DoS) via crafted messages.
AnalysisAI
CVE-2024-42646 is a segmentation fault vulnerability in NanoMQ v0.21.10 that allows unauthenticated remote attackers to trigger a denial of service condition by sending specially crafted messages. This is a network-accessible DoS vulnerability with high availability impact (CVSS 7.5) that affects message broker deployments. The vulnerability requires no authentication or user interaction, making it easily exploitable in production environments.
Technical ContextAI
NanoMQ is a lightweight MQTT message broker implementation. The vulnerability exists in the message parsing or processing logic (CWE-125: Out-of-bounds Read), where insufficient input validation on crafted MQTT protocol messages leads to a segmentation fault—typically caused by reading beyond allocated buffer boundaries. MQTT v3.1/v5.0 message handlers in NanoMQ v0.21.10 lack proper bounds checking when processing variable-length message fields (e.g., topic names, payloads, or protocol headers). This memory safety issue is common in C/C++ implementations lacking memory-safe abstractions. The segfault is triggered during message deserialization before protocol validation completes, allowing any network client to crash the broker process without establishing authenticated sessions.
RemediationAI
Immediate actions: (1) Upgrade NanoMQ to the latest patched version (vendor advisory required—check https://github.com/emqx/nanomq/releases and https://www.emqx.io/); (2) If upgrade is blocked, implement network-level mitigations: restrict MQTT broker access via firewall/ACLs to trusted clients only, isolate the broker on a segmented network, and disable public Internet exposure; (3) Monitor broker process health and implement automated restart mechanisms (systemd service files, container health checks) to minimize downtime from crash events; (4) Add input validation/fuzzing at the network boundary if running a custom reverse proxy. Workarounds are limited for this memory safety issue—patching is the primary mitigation.
NanoMQ 0.17.5 has a one-byte heap-based buffer over-read in the conn_handler function of mqtt_parser.c when it processes
Null Pointer Dereference vulnerability in topic_filtern function in mqtt_parser.c in NanoMQ 0.21.7 allows attackers to c
A use-after-free vulnerability exists in NanoMQ 0.17.2. Rated high severity (CVSS 7.5), this vulnerability is remotely e
A heap buffer overflow vulnerability exists in NanoMQ 0.17.2. Rated high severity (CVSS 7.5), this vulnerability is remo
A heap buffer overflow vulnerability exists in NanoMQ 0.17.2. Rated high severity (CVSS 7.5), this vulnerability is remo
A heap buffer overflow vulnerability exists in NanoMQ 0.17.2. Rated high severity (CVSS 7.5), this vulnerability is remo
In NanoMQ v0.15.0-0, segment fault with Null Pointer Dereference occurs in the process of decoding subinfo_decode and un
In NanoMQ v0.15.0-0, a Heap overflow occurs in copyn_utf8_str function of mqtt_parser.c. Rated high severity (CVSS 7.5),
In NanoMQ v0.15.0-0, Heap overflow occurs in read_byte function of mqtt_code.c. Rated high severity (CVSS 7.5), this vul
A heap-buffer-overflow vulnerability in the read_byte function in NanoMQ v.0.21.7 allows attackers to cause a denial of
NanoMQ v0.22.10 was discovered to contain a memory leak which allows attackers to cause a Denial of Service (DoS) via a
NanoMQ v0.22.10 was discovered to contain a heap overflow which allows attackers to cause a Denial of Service (DoS) via
Same weakness CWE-125 – Out-of-bounds Read
View allSame technique Denial Of Service
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2024-54786