CVE-2022-43761

9.4 CRITICAL

📋 TL;DR

CVE-2022-43761 is a critical authentication bypass vulnerability in B&R APROL industrial automation systems. It allows unauthenticated attackers to read and modify system configurations without credentials. This affects all B&R APROL installations running versions below R 4.2-07.

💻 Affected Systems

Products:
  • B&R APROL industrial automation system
Versions: All versions < R 4.2-07
Operating Systems: Industrial control system platforms running APROL
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the APROL database management interface specifically. Industrial control systems in manufacturing, energy, and critical infrastructure sectors are particularly at risk.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise allowing attackers to modify industrial control configurations, potentially causing physical damage, production disruption, or safety incidents.

🟠

Likely Case

Unauthorized access to sensitive configuration data and potential manipulation of industrial processes leading to operational disruption.

🟢

If Mitigated

Limited impact with proper network segmentation and access controls preventing external access to vulnerable systems.

🌐 Internet-Facing: HIGH - Direct internet exposure would allow remote attackers to exploit this without authentication.
🏢 Internal Only: HIGH - Even internally, any network access to the system allows exploitation without credentials.

🎯 Exploit Status

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

The vulnerability requires no authentication and minimal technical skill to exploit once the system is discovered.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: R 4.2-07 and later

Vendor Advisory: https://www.br-automation.com/downloads_br_productcatalogue/assets/1674823095245-en-original-1.0.pdf

Restart Required: Yes

Instructions:

1. Download APROL version R 4.2-07 or later from B&R Automation website. 2. Backup current configuration. 3. Install the update following vendor documentation. 4. Restart the APROL system. 5. Verify authentication is now required for database management.

🔧 Temporary Workarounds

Network Segmentation

all

Isolate APROL systems from untrusted networks using firewalls and VLANs

Access Control Lists

all

Implement strict network access controls to limit connections to APROL systems

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate APROL systems from all untrusted networks
  • Deploy intrusion detection systems to monitor for unauthorized access attempts to APROL interfaces

🔍 How to Verify

Check if Vulnerable:

Check APROL system version via the system interface or configuration files. If version is below R 4.2-07, the system is vulnerable.

Check Version:

Check APROL system documentation for version checking procedure specific to your installation

Verify Fix Applied:

After patching, verify version is R 4.2-07 or later and test that authentication is required for database management operations.

📡 Detection & Monitoring

Log Indicators:

  • Unauthenticated access attempts to database management endpoints
  • Configuration changes without corresponding authentication logs

Network Indicators:

  • Unusual traffic patterns to APROL database management ports
  • Connection attempts from unauthorized IP addresses

SIEM Query:

source="aprol_logs" AND (event_type="database_access" AND auth_status="failed") OR (event_type="config_change" AND user="unknown")

🔗 References

📤 Share & Export