Horizon Alert
Summary of the vulnerability and why it matters
A race condition in OpenPLC Runtime allows multiple concurrent requests to create unauthenticated administrator accounts. This vulnerability could allow unauthorized access to control system functions if the affected technology is exposed to external networks. The main concern is confirming relevance and exposure, as these systems are typically isolated.
- Unauthenticated admin accounts created.
- Critical for confirming operational technology exposure.
- Assess operational technology relevance and network exposure.
Attack Path
How an attacker could exploit the issue
An attacker can exploit this vulnerability by sending multiple concurrent requests to the OpenPLC Runtime over the network. The system's failure to properly check for the existence of users before committing them allows an attacker to bypass authentication and create several unauthenticated administrative accounts. This could potentially lead to unauthorized control or manipulation of the industrial automation system.
- Unauthenticated network access required.
- Race condition in user existence check.
- Risk of unauthorized administrative control.
Live Threat
Current exploitation, exposure, and threat context
When supported by the advisory, a race condition in Autonomy Logic OpenPLC Runtime could allow multiple concurrent requests to bypass existence checks, leading to the creation of several unauthenticated administrator accounts. This could potentially grant unauthorized users administrative access to the system.
- System data and configuration could be at risk.
- Unauthenticated access could occur over the network.
- Unauthorized administrative control may result.
Operational Fix
Recommended remediation, mitigation, and detection steps
The Autonomy Logic OpenPLC Runtime vulnerability impacts systems controlling industrial processes. Ownership likely falls to the industrial control system (ICS) or operational technology (OT) teams, possibly with support from infrastructure or vendor management if the product was procured. The immediate first step is to identify all deployed instances of OpenPLC Runtime, determine their network exposure and criticality, and then initiate a coordinated response aligned with operational risk and maintenance schedules.
- ICS/OT teams own this issue.
- Verify network exposure and criticality.
- Plan remediation based on risk.