Infracost: Terraform Cloud and registry token disclosure via unvalidated hostname
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| infracost | infracost | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Infracost | Infracost |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-6x6c-w9w9-hv4h | Infracost: Terraform Cloud and registry token disclosure via unvalidated hostname |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.500% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Infracost
Infracost infracost |
|
| Vendors & Products |
Infracost
Infracost infracost |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Infracost provides cloud cost intelligence for engineers, AI coding agents, and CI/CD. Prior to 0.10.45, internal/hcl/remote_variables_loader.go and related Terraform Cloud, remote-plan, and Terragrunt registry request paths can attach a configured Terraform Cloud or registry token to a destination hostname derived from untrusted Terraform input without confirming that it is the configured trusted host. When a CI run provides a token while scanning attacker-controlled Terraform, including pull_request_target or a same-repository pull request, an attacker can direct the request to an attacker-controlled host and disclose the token. Standard fork pull_request workflows without secrets are not exposed. This issue is fixed in version 0.10.45. | |
| Title | Infracost: Terraform Cloud and registry token disclosure via unvalidated hostname | |
| Weaknesses | CWE-522 | |
| References |
| |
| Metrics |
cvssV4_0
|