CVE-2024-48077
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2026-01-15

Last updated on: 2026-04-03

Assigner: MITRE

Description
NanoMQ v0.22.7 is vulnerable to Denial of Service (DoS) due to improper resource throttling. A crafted sequence of requests causes the recv-q queue to saturate, leading to the rapid exhaustion of system file descriptors (FDs). This exhaustion triggers a process crash, rendering the broker unable to provide services.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-15
Last Modified
2026-04-03
Generated
2026-06-16
AI Q&A
2026-01-16
EPSS Evaluated
2026-06-14
NVD
CVE-2024-48077
EUVD
EUVD-2026-2717
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
nanomq nanomq 0.22.7
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-400 The product does not properly control the allocation and maintenance of a limited resource.
CWE-833 The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2024-48077 is a Denial of Service (DoS) vulnerability in nanomq version 0.22.7. An attacker can send a large number of crafted MQTT packets to the nanomq broker, causing the recv-q queue to grow rapidly. This leads to excessive consumption of file descriptor resources, exhausting them and causing the nanomq broker to collapse and become unable to provide normal services. [1]

Impact Analysis

This vulnerability can cause the nanomq broker to enter a deadlock state and become unresponsive, resulting in a Denial of Service. This means that normal services provided by the broker will be unavailable, potentially disrupting any systems or applications relying on nanomq for message brokering. [1]

Detection Guidance

This vulnerability can be detected by monitoring the nanomq process's recv-q queue size and file descriptor usage. A rapid increase in the number of data packets in the recv-q queue or exhaustion of file descriptors indicates a potential attack. Commands such as 'netstat -anp | grep nanomq' to check network connections, and 'lsof -p <nanomq_pid>' to monitor open file descriptors can help detect abnormal behavior. Additionally, monitoring MQTT traffic volume for unusually high packet rates may indicate exploitation attempts. [1]

Mitigation Strategies

Immediate mitigation steps include limiting the rate of incoming MQTT packets to the nanomq broker to prevent recv-q queue overflow, applying network-level filtering or rate limiting to block suspicious traffic, and monitoring file descriptor usage to detect early signs of exhaustion. Updating nanomq to a version that addresses this vulnerability, if available, is also recommended. [1]

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2024-48077. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart