Code execution via malicious Terraform file deserialization
Published Apr 20, 2021 · Updated Sep 17, 2024
Unsafe deserialization in Palo Alto Networks Checkov before 2.0.26 allows remote attackers to execute code through a malicious Terraform file. Palo Alto Networks has not disclosed the deserializer, code path, or specific unsafe operation beyond identifying Terraform-file processing. Reachability requires high privileges and a scan of attacker-controlled Terraform; resulting code inherits the Checkov process's privileges.
Summary
What happened
Unsafe deserialization in Palo Alto Networks Checkov before 2.0.26 allows remote attackers to execute code through a malicious Terraform file. Palo Alto Networks has not disclosed the deserializer, code path, or specific unsafe operation beyond identifying Terraform-file processing. Reachability requires high privileges and a scan of attacker-controlled Terraform; resulting code inherits the Checkov process's privileges.
The record
- CVE
- CVE-2021-3035
- Published
- Apr 20, 2021
- Updated
- Sep 17, 2024
- Vendor
- Palo Alto Networks
- Product
- Checkov
- Classifications
- CWE-502, T1203
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Apr 20, 2021CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0 <2.0.26 changes=[{"at":"2.0.26","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo