Horizon Alert
Summary of the vulnerability and why it matters
A critical vulnerability has been identified in WebErpMesv2, an industrial resource management and manufacturing execution system. This flaw allows for unauthenticated remote code execution, meaning an attacker could potentially gain control of affected systems without needing any credentials. This impacts systems that are not yet updated to address the issue.
- Unauthenticated attackers can execute code remotely.
- Critical vulnerability in industrial control system.
- Confirm relevance and confirm exposure to this threat.
Attack Path
How an attacker could exploit the issue
An attacker can initiate a campaign by exploiting a vulnerability in the WebErpMesv2 system, which is a web-based manufacturing and resource management tool. The system's open registration and flawed security checks allow an unauthenticated attacker to upload malicious PHP files. This upload is facilitated through the `HR Expense scan_file` parameter, bypassing intended security controls and ultimately leading to the execution of arbitrary code on the server.
- No authentication required for initial access.
- Upload arbitrary PHP files via a specific parameter.
- Achieves unauthenticated Remote Code Execution.
Live Threat
Current exploitation, exposure, and threat context
A self-registered user could upload arbitrary PHP files, potentially leading to unauthenticated remote code execution on systems with default configurations and no additional security measures. This could affect the integrity and availability of the manufacturing execution system.
- System data and code.
- Uploading malicious PHP files.
- Unauthorized system access and control.
Operational Fix
Recommended remediation, mitigation, and detection steps
Given that WebErpMesv2 is a web-based manufacturing execution system, application owners and platform teams are likely responsible for addressing this vulnerability. The initial practical step involves identifying all instances of WebErpMesv2 within the environment, determining their reachability and business criticality, and then locating the accountable owner to initiate a risk-based remediation plan.
- Application owners should take ownership.
- Verify external exposure and reachability first.
- Plan remediation based on business impact.