{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-48077 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-48077 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-48077 is a high-severity denial of service vulnerability in n/a, published on 15 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-48077 and fix it if it is affected.\n\nWhat it is: CVE-2024-48077 is a high-severity denial of service vulnerability in n/a, published on 15 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-48077 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-48077/ (Markdown: https://insights.sbomify.com/CVE-2024-48077/index.md)","id":"CVE-2024-48077","markdown":"https://insights.sbomify.com/CVE-2024-48077/index.md","name":"CVE-2024-48077","record":{"aliases":["GHSA-4f8h-hq55-xrp6"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"MQTT broker","requires_auth":"none","summary":"Attackers can crash the NanoMQ broker by exhausting file descriptors through crafted requests, causing service unavailability.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nanomq","vendor":"emqx"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-833","name":"Deadlock"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Denial of service in n/a","id":"CVE-2024-48077","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2024-48080"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2024-48075"},"products":["n/a"],"published":"2026-01-15","related":[{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2024-42655","kev_date_added":null,"published":"2025-07-29"},{"cvss_score":8.5,"headline":"NanoMQ has Buffer Overflow","id":"CVE-2025-59947","kev_date_added":null,"published":"2025-12-15"},{"cvss_score":8,"headline":"Memory corruption in n/a","id":"CVE-2023-34488","kev_date_added":null,"published":"2023-06-12"},{"cvss_score":7.7,"headline":"NanoMQ has Heap Buffer Overflow in URI Parameter Parsing","id":"CVE-2026-32135","kev_date_added":null,"published":"2026-04-20"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2026-36590","kev_date_added":null,"published":"2026-07-15"},{"cvss_score":7.5,"headline":"MQTT v5 Variable Byte Integer parsing out-of-bounds: get_var_integer()","id":"CVE-2026-21888","kev_date_added":null,"published":"2026-03-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-03","vendors":["n/a"]},"summary":"Attackers can crash the NanoMQ broker by exhausting file descriptors through crafted requests, causing service unavailability.","url":"https://insights.sbomify.com/CVE-2024-48077/"}