CVE-2025-2180
BaseFortify
Publication date: 2025-08-13
Last updated on: 2025-08-13
Assigner: Palo Alto Networks, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| palo_alto_networks | checkov | 3.2.415 |
| palo_alto_networks | checkov | 3.2.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-502 | The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an unsafe deserialization flaw in Palo Alto Networks Checkov by Prisma Cloud, affecting versions before 3.2.415. It allows an authenticated user to execute arbitrary code as a non-administrative user by scanning a malicious Terraform file with Checkov. The attack requires no special privileges and is of low complexity, exploiting the deserialization of untrusted data. [1]
How can this vulnerability impact me? :
If exploited, this vulnerability could allow an authenticated user to run arbitrary code on the system as a non-administrative user by scanning a malicious Terraform file. This could lead to unauthorized actions or compromise of the environment where Checkov is used. However, the severity is rated low, and no active exploitation is known. The risk increases if scanning infrastructure as code files from untrusted sources. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by identifying if your environment is running a vulnerable version of Checkov (versions earlier than 3.2.415) within Prisma Cloud. Since the vulnerability occurs when scanning malicious Terraform files, detection involves verifying the Checkov version and monitoring for scans of untrusted Terraform files. Specific commands are not provided in the resources, but checking the installed Checkov version can be done with a command like 'checkov --version'. Additionally, reviewing logs for scans of suspicious Terraform files may help detect exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include upgrading Checkov to version 3.2.415 or later. Additionally, avoid running Checkov scans on Terraform files from untrusted sources or pull requests to reduce the risk of exploitation. [1]