Horizon Alert
Summary of the vulnerability and why it matters
Terrascan, when running in server mode, has a flaw that allows attackers to trick it into fetching malicious content from external URLs. This could lead to unauthorized access to sensitive information or potentially other system compromises. Because Terrascan was archived and is no longer maintained, there will be no fix.
- Can read local files.
- Exploitable remotely without authentication.
- Affects deployments running Terrascan in server mode.
Attack Path
How an attacker could exploit the issue
An unauthenticated remote attacker can exploit this vulnerability by uploading a specially crafted Infrastructure as Code (IaC) template to a Terrascan server. This template will contain a malicious URL that Terrascan will fetch server-side, allowing the attacker to read local files on the server or potentially access other internal resources.
- Server mode is required.
- Unauthenticated remote access is needed.
- Malicious IaC template upload.
Live Threat
Current exploitation, exposure, and threat context
This SSRF vulnerability in Terrascan is concerning due to its potential for local file reading and server-side request forgery. While Terrascan has been archived, meaning no official patches will be released, its unauthenticated server mode makes it a tempting target. Attackers might exploit this to access sensitive information or pivot to other internal systems, particularly if deployed in insecure environments.
- Unauthenticated server mode is vulnerable.
- Local file read is possible.
- No official patch will be released.
Priority actions
Operational Fix
Recommended remediation, mitigation, and detection steps
Focus on detecting and blocking external URL resolution attempts within uploaded IaC templates when running Terrascan in server mode. Since Terrascan is archived and unpatched, prioritize isolating or disabling any instances of Terrascan running in server mode. Monitor network traffic for any outbound connection attempts from Terrascan instances, specifically those originating from template processing.
- Block external URL resolutions.
- Isolate or disable Terrascan server instances.
- Monitor for suspicious outbound connections.