CVE-2022-30319

8.1 HIGH

📋 TL;DR

This vulnerability allows attackers to bypass authentication on Saia Burgess Controls (SBC) PCD controllers by spoofing UDP traffic on port 5050. Organizations using these industrial control system devices for building automation and process control are affected. Attackers can access sensitive engineering functions like uploading/downloading control logic and manipulating controller configurations.

💻 Affected Systems

Products:
  • Saia Burgess Controls (SBC) PCD controllers
Versions: All versions through 2022-05-06
Operating Systems: Embedded controller firmware
Default Config Vulnerable: ⚠️ Yes
Notes: Affects controllers using S-Bus protocol (5050/UDP) with password protection enabled. The vulnerability exists in the authentication mechanism itself.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of industrial control systems allowing attackers to modify control logic, disrupt operations, cause physical damage, or establish persistent access to critical infrastructure.

🟠

Likely Case

Unauthorized access to controller configurations and logic, potentially leading to operational disruption, data theft, or preparation for future attacks.

🟢

If Mitigated

Limited impact if proper network segmentation and monitoring are in place, though authentication bypass remains possible.

🌐 Internet-Facing: HIGH
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Attack requires ability to observe network traffic to capture authenticated client MAC/IP addresses, then spoof UDP packets. No authentication needed to initiate attack.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Firmware updates after 2022-05-06

Vendor Advisory: https://www.cisa.gov/uscert/ics/advisories/icsa-22-207-03

Restart Required: Yes

Instructions:

1. Contact Saia Burgess Controls for updated firmware. 2. Backup current configuration. 3. Apply firmware update following vendor instructions. 4. Restart controller. 5. Verify authentication is functioning correctly.

🔧 Temporary Workarounds

Network segmentation and firewall rules

all

Restrict access to S-Bus port 5050/UDP to only authorized engineering workstations and networks.

Network monitoring and anomaly detection

all

Monitor UDP traffic on port 5050 for spoofing attempts and unauthorized access patterns.

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate SBC controllers from untrusted networks
  • Deploy network monitoring and intrusion detection specifically for S-Bus protocol traffic on port 5050/UDP

🔍 How to Verify

Check if Vulnerable:

Check controller firmware version date. If before or equal to 2022-05-06, the system is vulnerable. Also test authentication bypass by attempting to spoof UDP packets to port 5050 after observing legitimate traffic.

Check Version:

Check through SBC engineering software interface or consult vendor documentation for version checking procedure.

Verify Fix Applied:

Verify firmware version is after 2022-05-06. Test that authentication cannot be bypassed by spoofing UDP packets even after observing legitimate authenticated traffic.

📡 Detection & Monitoring

Log Indicators:

  • Multiple authentication attempts from same MAC/IP with different source addresses
  • Unauthorized access to engineering functions

Network Indicators:

  • UDP traffic on port 5050 from unexpected sources
  • Spoofed MAC/IP addresses in S-Bus protocol traffic

SIEM Query:

source_port:5050 AND protocol:udp AND (src_mac_changed OR src_ip_spoofed)

🔗 References

📤 Share & Export