Summary
Service information between WebCTRL and BACnet-based PLCs is transmitted in cleartext, allowing an attacker on the network to sniff, intercept, and modify packets in transit.
Because file transfer metadata and proprietary update formats are not encrypted or integrity-protected, an attacker can observe file positions and data contents, and potentially reverse engineer and tamper with controller updates.
Affected context
This vulnerability arises in building automation or industrial environments where WebCTRL communicates with PLCs using BACnet over IP without transport-layer protection.
Any segment of the network where BACnet traffic is routable and unencrypted becomes a potential observation and injection point, including shared VLANs, flat OT networks, or poorly segmented corporate networks.
The risk is higher in deployments where controllers are updated or configured over the same cleartext channel that carries operational data.
Exploit preconditions
- Attack surface: Network-level BACnet traffic between WebCTRL and PLCs (typically BACnet/IP).
- Required access: Ability to observe or access the same network segment or routing path where BACnet packets transit (e.g., local LAN access, compromised router/switch, span/mirror ports, or man-in-the-middle position).
- Trigger point: Normal operation, file transfer, or update workflows where WebCTRL exchanges service information, including file start positions and file data, with controllers.
- Why exploitation is possible: The protocol exchanges sensitive operational and file-transfer information in cleartext, without encryption or cryptographic integrity checks, enabling both passive sniffing and active packet modification.
Why this happens
The core issue aligns with CWE-319: Cleartext Transmission of Sensitive Information.
BACnet traffic carrying WebCTRL service data, including file transfer metadata and contents, is transmitted without confidentiality or integrity protection at the transport or application layer.
This design assumes a trusted network and offers no native defense against packet capture or manipulation, allowing attackers on the path to eavesdrop and tamper with critical device communication.
Potential impact
- Passive disclosure of sensitive operational information, including file start positions and file data transmitted between WebCTRL and PLCs.
- Reverse engineering of the proprietary WebCTRL update or file-transfer format by analyzing captured traffic.
- Unauthorized modification of in-flight BACnet packets, potentially altering file contents, parameters, or controller state.
- Injection of crafted BACnet messages that may corrupt configurations, disrupt service, or cause unsafe equipment behavior.
- Foundation for more advanced attacks such as controller compromise, long-term persistence in building automation systems, or broader OT network manipulation.
General mitigation guidance
Effective mitigation focuses on adding confidentiality and integrity protections around BACnet/WebCTRL traffic and reducing exposure of OT communications:
- Introduce secure transport overlays such as VPN tunnels or mutually authenticated secure gateways for BACnet/IP segments that traverse shared or untrusted networks.
- Enforce strict network segmentation between IT and OT, and between different building or controller zones, using firewalls that explicitly restrict BACnet traffic flows.
- Limit physical and logical access to switches, routers, and wireless infrastructure that carry BACnet packets, and use managed switches with port security and monitoring.
- Where possible, prefer architectures that wrap controller update channels in cryptographically protected protocols, or use secure management networks isolated from general-purpose traffic.
- Apply least-privilege principles to service accounts and management stations, ensuring that only designated hosts can initiate update or file-transfer operations.
How teams detect issues like this
Detection typically involves monitoring network paths and configuration baselines rather than relying solely on endpoint behavior:
- Use network intrusion detection systems (NIDS) or protocol-aware monitoring tools with BACnet dissectors to identify unencrypted BACnet traffic on segments that should be isolated or secured.
- Establish baseline profiles of expected BACnet communication (endpoints, ports, message types) and alert on anomalies such as new talkers, unexpected file transfers, or unusual BACnet service usage.
- Perform periodic network scans and architectural reviews to identify BACnet/IP exposure beyond intended OT segments, including traversals into corporate or guest networks.
- During security assessments and code reviews of associated tooling, flag assumptions of "trusted networks" and lack of encryption or message authentication around controller update workflows.
- Incorporate automated policy checks in OT change management processes to ensure new deployments or topology changes do not inadvertently expose BACnet traffic to broader network visibility.

