EUVD-2024-54786Severity 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
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
Share
External POC / Exploit Code
Leaving vuln.today