{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66624 exists.","fix":"No fix has been published for CVE-2025-66624 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-66624 is a high-severity denial of service vulnerability in bacnet-stack, published on 5 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-66624 and fix it if it is affected.\n\nWhat it is: CVE-2025-66624 is a high-severity denial of service vulnerability in bacnet-stack, published on 5 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66624 exists.\n\nAffected product: bacnet-stack. 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-2025-66624/ (Markdown: https://insights.sbomify.com/CVE-2025-66624/index.md)","id":"CVE-2025-66624","markdown":"https://insights.sbomify.com/CVE-2025-66624/index.md","name":"CVE-2025-66624","record":{"aliases":["GHSA-8wgw-5h6x-qgqg"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"BACnet protocol stack","requires_auth":"none","summary":"An out-of-bounds read in the BACnet stack allows attackers to cause a denial of service via malformed packets.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"bacnet_stack","vendor":"bacnetstack"}],"cvss":{"score":7.5,"severity":"high","source":"cna","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-125","name":"Out-of-bounds Read"}],"description":"BACnet Protocol Stack library provides a BACnet application layer, network layer and media access (MAC) layer communications services. Prior to 1.5.0.rc2, The npdu_is_expected_reply function in src/bacnet/npdu.c indexes request_pdu[offset+2/3/5] and reply_pdu[offset+1/2/4] without verifying that those APDU bytes exist. bacnet_npdu_decode() can return offset == 2 for a 2-byte NPDU, so tiny PDUs pass the version check and then get read out of bounds. On ASan/MPU/strict builds this is an immediate crash (DoS). On unprotected builds it is undefined behavior and can mis-route replies; RCE is unlikely because only reads occur, but DoS is reliable.","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":"BACnet-stack MS/TP reply matcher OOB read","id":"CVE-2025-66624","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Umbraco Vulnerable to Improper File Access and Credential Exposure through Dictionary Import Functionality","id":"CVE-2025-66625"},"packages":[],"prev":{"headline":"Strimzi allows unrestricted access to all Secrets in the same Kubernetes namespace from Kafka Connect and MirrorMaker 2 operands","id":"CVE-2025-66623"},"products":["bacnet-stack"],"published":"2025-12-05","related":[{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2023-51773","kev_date_added":null,"published":"2023-12-25"},{"cvss_score":8.7,"headline":"BACnet Stack: Out-of-Bounds Read in WritePropertyMultiple Decoder via Deprecated Tag Parser","id":"CVE-2026-41475","kev_date_added":null,"published":"2026-04-24"},{"cvss_score":8.7,"headline":"BACnet Stack: Off-by-One Out-of-Bounds Read in ReadPropertyMultiple Object ID Decoder","id":"CVE-2026-41502","kev_date_added":null,"published":"2026-04-24"},{"cvss_score":8.7,"headline":"BACnet Stack: Out-of-Bounds Read in ReadPropertyMultiple Property Decoder via Deprecated Tag Parser","id":"CVE-2026-41503","kev_date_added":null,"published":"2026-04-24"},{"cvss_score":7.8,"headline":"BACnet Stack WriteProperty decoding length underflow leads to OOB read and crash","id":"CVE-2026-26264","kev_date_added":null,"published":"2026-02-13"},{"cvss_score":7.5,"headline":"BACnet Stack Improperly Limits Pathnames to a Restricted Directory","id":"CVE-2026-21878","kev_date_added":null,"published":"2026-02-13"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-08","vendors":["bacnet-stack"]},"summary":"An out-of-bounds read in the BACnet stack allows attackers to cause a denial of service via malformed packets.","url":"https://insights.sbomify.com/CVE-2025-66624/"}