Horizon Alert
Summary of the vulnerability and why it matters
This advisory concerns a critical vulnerability in an operation and maintenance audit and risk control system that could allow an attacker to create new user accounts and potentially take over the system. The vulnerability, identified as server-side request forgery, stems from how the system handles specially crafted XML-RPC requests. Attackers can exploit this to execute administrative functions through internal communication channels, bypassing normal security controls.
- System flaw allows unauthorized account creation.
- High-impact target for unauthorized system access.
- Confirm relevance and assess exposure of this system.
Attack Path
How an attacker could exploit the issue
An attacker can exploit this vulnerability by sending specially crafted XML-RPC requests to the system's xmlrpc.sock handler. This allows them to trick the server into interacting with internal RPC endpoints. By doing so, an attacker can execute privileged XML-RPC methods that are normally inaccessible, leading to the creation of new user accounts and potentially full control over the system.
- Accessible via the network.
- Triggered by sending malicious XML-RPC requests.
- Allows arbitrary user account creation.
Live Threat
Current exploitation, exposure, and threat context
This vulnerability could allow an unauthenticated attacker to send specially crafted requests to the Anheng Mingyu Operation and Maintenance Audit and Risk Control System. When supported by the advisory's configuration, these requests could trick the system into interacting with its own internal RPC endpoints. This could lead to the creation of arbitrary user accounts, potentially giving an attacker control over the bastion host.
- Arbitrary user accounts on system.
- Attacker sends crafted XML-RPC requests.
- Bastion host takeover is possible.
Operational Fix
Recommended remediation, mitigation, and detection steps
The Anheng Mingyu Operation and Maintenance Audit and Risk Control System, often deployed as a bastion host or management portal, is susceptible to a critical Server-Side Request Forgery vulnerability. Attackers can exploit this to perform privileged actions and potentially gain full control of the system. The first practical step involves identifying all instances of this system, confirming their network reachability and business criticality, and locating the accountable owner. Subsequently, a remediation plan should be developed based on the identified risk.
- Ownership: Infrastructure or security operations teams.
- Verify: System reachability and business criticality.
- Action: Plan and coordinate remediation efforts.