Horizon Alert
Summary of the vulnerability and why it matters
A vulnerability in AudioCodes Fax Server and Auto-Attendant IVR appliances could allow an unauthenticated remote attacker to execute arbitrary commands on affected systems. This is due to an insecure backup upload feature that does not validate file types or authenticate users, potentially enabling the upload of malicious configuration files that could lead to system compromise.
- Unauthenticated file upload allows code execution.
- Critical risk to appliance integrity and operations.
- Confirm relevance and assess exposure to appliances.
Attack Path
How an attacker could exploit the issue
An attacker can leverage an unauthenticated backup upload feature to execute arbitrary code on the server. This is possible by uploading a specially crafted configuration file that the server then misinterprets as executable code, leading to command execution with high privileges.
- No authentication required.
- Upload malicious configuration file.
- Arbitrary code execution.
Live Threat
Current exploitation, exposure, and threat context
On AudioCodes Fax Server and Auto-Attendant IVR appliances, an unauthenticated backup upload vulnerability could allow a remote attacker to execute arbitrary commands. This is possible when the backup directory is configured to reside on the system drive in Windows deployments, enabling the upload of malicious configuration files that are then treated as executable code by the web server.
- Server configuration files.
- Uploading malicious files to specific paths.
- Arbitrary command execution as SYSTEM.
Operational Fix
Recommended remediation, mitigation, and detection steps
The AudioCodes Fax Server and IVR appliances are likely managed by infrastructure or platform teams responsible for maintaining these dedicated communication appliances, with potential oversight from network and security teams due to their external-facing nature. The first practical step is to locate all deployed instances, determine their exposure and criticality, identify the accountable owner, and then develop a remediation plan based on these findings.
- Infrastructure and platform teams own remediation.
- Verify appliance exposure and business criticality.
- Coordinate vendor patching and plan deployment.