Horizon Alert
Summary of the vulnerability and why it matters
A security issue in Trivy, a popular security scanner, allowed an attacker to publish malicious versions of the software and related GitHub Actions. This incident, an escalation of a prior supply chain attack, could expose sensitive information processed by affected pipelines. Teams should review their use of Trivy and associated tools immediately to prevent potential compromise.
- Sensitive data in pipelines may be exposed.
- Malicious code was distributed via software updates.
- This impacts software development workflows.
Attack Path
How an attacker could exploit the issue
An attacker with prior access, likely from an earlier credential compromise, can inject malicious code into a popular security scanner and its associated GitHub Actions. This allows them to poison the software supply chain, leading to sensitive information exposure for anyone using the compromised versions in their CI/CD pipelines.
- Requires prior access.
- Targets Trivy tooling.
- Exposes CI/CD secrets.
Live Threat
Current exploitation, exposure, and threat context
Attackers are likely to target this vulnerability due to its supply chain nature, which can lead to widespread compromise. The specific incident involved compromised credentials to inject malicious code into widely used development tools. This allows attackers to potentially access sensitive information within CI/CD environments, making it an attractive target.
- KEV listed
- Supply chain attack vector
- Recent incident activity
Priority actions
Operational Fix
Recommended remediation, mitigation, and detection steps
Prioritize immediate actions to identify and contain the supply chain compromise. Teams must thoroughly review all workflows that utilized the affected `aquasecurity/trivy-action` and `aquasecurity/setup-trivy` GitHub Actions, especially if version tags, not commit SHAs, were used. Treat all secrets accessible to these pipelines as potentially exposed and initiate rotation immediately, focusing on repositories named `tpcp-docs` as an indicator of exfiltration.
- Remove affected Trivy artifacts immediately.
- Rotate all secrets accessed by affected pipelines.
- Pin GitHub Actions to immutable commit SHAs.
