Horizon Alert
Summary of the vulnerability and why it matters
A vulnerability in Broadcom AutoSys Workload Automation's Workload Control Center modules on Windows and Linux could allow for object injection through the deserialization of untrusted data. This issue impacts versions of AutoSys Workload Automation from 12.1 through 24.0.01.
- Allows attackers to inject malicious code.
- Affects critical workload automation management.
- Confirm if AutoSys Workload Automation is in use.
Attack Path
How an attacker could exploit the issue
Attackers can target the Workload Control Center (WCC) of Broadcom AutoSys Workload Automation, a web-based management interface, without needing any prior authentication or access. By exploiting a deserialization vulnerability, an attacker could inject malicious objects into the system, leading to significant compromise.
- Accessible via the network.
- Triggers through data deserialization.
- Allows object injection and full compromise.
Live Threat
Current exploitation, exposure, and threat context
A deserialization of untrusted data vulnerability in Broadcom AutoSys Workload Automation's Workload Control Center (WCC) modules could allow for object injection when supported. This means that an attacker could potentially inject malicious objects into the system, impacting its behavior.
- System integrity could be affected.
- Untrusted data could be deserialized.
- Service behavior may be altered.
Operational Fix
Recommended remediation, mitigation, and detection steps
The Workload Control Center (WCC) is likely managed by application owners and platform teams, with support from network and security teams. The first practical step is to identify all WCC instances, determine their accessibility and business criticality, and then assign ownership for remediation planning based on risk.
- Application and platform teams own the issue.
- Verify WCC instances and exposure.
- Plan risk-based remediation actions.