CVE-2026-62974 in Bacnet Stack
Summary
by MITRE • 11/13/2026
BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.5, 1.5.1, and 1.6.0, a malformed but non-empty BACnet WriteProperty request can drive the official server demo into a non-terminating request-processing loop with repeated heap-backed side effects. This results in a remote unauthenticated denial of service via uncontrolled resource consumption and a non-terminating request path. This issue has been patched in versions 1.4.5, 1.5.1, and 1.6.0.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 11/13/2026
The BACnet Stack is an open-source C library designed to implement the Building Automation and Control Networks protocol for embedded systems. As a foundational component for IoT devices in smart buildings, it handles critical communication between controllers, sensors, and management stations. The vulnerability identified affects versions prior to 1.4.5, 1.5.1, and 1.6.0 of this stack. It specifically targets the request processing logic within the official server demonstration implementation when handling WriteProperty requests. This flaw represents a significant risk to the availability of building automation systems that rely on this software for real-time control and monitoring.
The technical root cause lies in how the parser handles malformed but non-empty BACnet WriteProperty messages. When such a request is received, the internal logic fails to properly validate or terminate the processing sequence under specific edge cases involving invalid data structures. Instead of rejecting the packet with an appropriate error code, the server enters a non-terminating loop. This infinite execution path consumes CPU cycles continuously and triggers repeated heap allocations for temporary buffers associated with parsing the malformed input. The lack of bounds checking or state reset mechanisms allows this condition to persist indefinitely as long as the connection remains open.
From an operational perspective, this vulnerability enables a remote unauthenticated denial-of-service attack. An attacker does not need valid credentials to exploit this flaw; they merely need network access to send the crafted packet. Once triggered, the server becomes unresponsive due to resource exhaustion and CPU saturation. In building automation contexts, where timely response is critical for HVAC control, security systems, or fire alarms, such a hang can lead to significant operational disruptions. The repeated heap-backed side effects may also eventually cause memory corruption if the system's garbage collection or memory management cannot keep pace with the rapid allocation rate, potentially leading to further instability beyond simple service unavailability.
This vulnerability aligns with CWE-835, which describes loops that do not terminate correctly due to missing exit conditions or incorrect loop control variables. It also maps to MITRE ATT&CK technique T1499, specifically Endpoint Denial of Service via resource exhaustion. The attack vector is classified as Network-based and Unauthenticated, allowing adversaries with basic networking knowledge to disrupt services without prior access privileges. This highlights the importance of input validation in network-facing protocols where untrusted data is processed directly by embedded devices often lacking robust security controls.
Mitigation strategies primarily involve upgrading the BACnet Stack library to patched versions 1.4.5, 1.5.1, or 1.6.0 and later, which contain fixes for this parsing logic error. For systems that cannot be immediately updated, network-level mitigations should be implemented. Deploying access control lists on firewalls or routers to restrict BACnet traffic (typically UDP port 4780) to only known, trusted IP addresses can prevent unauthorized actors from sending malicious packets. Additionally, implementing deep packet inspection at the perimeter can help identify and drop malformed protocol messages before they reach the vulnerable server instance. Regular security audits of embedded firmware updates are essential to ensure these patches remain applied as new vulnerabilities emerge in IoT ecosystems.