{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-33656 exists.","fix":"No fix has been published for CVE-2023-33656 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-33656 is a medium-severity denial of service vulnerability in n/a, published on 30 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-33656 and fix it if it is affected.\n\nWhat it is: CVE-2023-33656 is a medium-severity denial of service vulnerability in n/a, published on 30 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-33656 exists.\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-2023-33656/ (Markdown: https://insights.sbomify.com/CVE-2023-33656/index.md)","id":"CVE-2023-33656","markdown":"https://insights.sbomify.com/CVE-2023-33656/index.md","name":"CVE-2023-33656","record":{"aliases":["GHSA-9479-9c7f-xq65"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MQTT broker","requires_auth":"none","summary":"An attacker can cause a denial of service in NanoMQ by triggering a memory leak that exhausts system resources.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nanomq","vendor":"emqx"}],"cvss":{"score":5.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"A memory leak vulnerability exists in NanoMQ 0.17.2. The vulnerability is located in the file message.c. An attacker could exploit this vulnerability to cause a denial of service attack by causing the program to consume all available memory resources.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Denial of service in n/a","id":"CVE-2023-33656","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Use after free in n/a","id":"CVE-2023-33657"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2023-33653"},"products":["n/a"],"published":"2023-05-30","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"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2024-48077","kev_date_added":null,"published":"2026-01-15"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-10","vendors":["n/a"]},"summary":"An attacker can cause a denial of service in NanoMQ by triggering a memory leak that exhausts system resources.","url":"https://insights.sbomify.com/CVE-2023-33656/"}