CVE-2020-36872: BACnet Test Server 1.01 Malformed BVLC Length DoS
BACnet Test Server versions up to and including 1.01 contains a remote denial of service vulnerability in its BACnet/IP BVLC packet handling. The server fails to properly validate the BVLC Length field in incoming UDP BVLC frames on the default BACnet port (47808/udp). A remote unauthenticated attacker can send a malformed BVLC Length value to trigger an access violation and crash the application, resulting in a denial of service.
Security readout for executives and security teams
Plain-English summary
BACnet Test Server can be crashed remotely by malformed BACnet/IP traffic. The issue is denial of service, not data theft or code execution, but it can still disrupt testing or exposed operational environments using this server.
Executive priority
Prioritize if BACnet Test Server is exposed beyond a controlled lab or management network. For isolated test-only deployments, urgency is lower but remediation should still be tracked.
Technical view
The vulnerability is in BACnet/IP BVLC packet handling. Sources state the server does not properly validate the BVLC Length field in UDP BVLC frames on port 47808, causing an access violation and application crash. Reported affected scope is BACnet Test Server up to and including 1.01, though supplied affected metadata is inconsistent.
Likely exposure
Exposure is likely limited to environments running BACnet Test Server, especially if BACnet/IP UDP 47808 is reachable from untrusted networks. This should not be assumed to affect all BACnet products.
Exploitation context
The source bundle includes public exploit references, but CISA KEV status is false and no cited source states active exploitation. Treat exploitability as publicly demonstrated, not confirmed in-the-wild exploitation.
Researcher notes
Do not generalize this to building controllers or other BACnet stacks without evidence. Version evidence is imperfect: narrative says through 1.01, while structured affected data lists version 0 with defaultStatus unaffected.
Mitigation direction
Check vendor guidance for fixed versions, replacement builds, or official mitigation advice.
Remove or disable BACnet Test Server where it is not required.
Restrict UDP 47808 exposure to trusted management or test networks only.
Block untrusted BACnet/IP traffic at network boundaries.
Monitor for unexpected crashes or restarts of the test server process.
Validation and detection
Inventory systems running BACnet Test Server and record exact versions.
Confirm whether UDP 47808 is reachable from untrusted networks.
Review crash logs for access violations in the BACnet Test Server process.
Compare installed versions against vendor or CVE guidance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-400 · source CWE mapping
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.