HashiCorp Terraform
By the Year
In 2023 there have been 1 vulnerability in HashiCorp Terraform with an average score of 7.8 out of ten. Terraform did not have any published security vulnerabilities last year. That is, 1 more vulnerability have already been reported in 2023 as compared to last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2023 | 1 | 7.80 |
| 2022 | 0 | 0.00 |
| 2021 | 1 | 8.80 |
| 2020 | 0 | 0.00 |
| 2019 | 1 | 7.50 |
| 2018 | 1 | 9.80 |
It may take a day or so for new Terraform vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent HashiCorp Terraform Security Vulnerabilities
Terraform version 1.0.8 through 1.5.6
CVE-2023-4782
7.8 - High
- September 08, 2023
Terraform version 1.0.8 through 1.5.6 allows arbitrary file write during the `init` operation if run on maliciously crafted Terraform configuration. This vulnerability is fixed in Terraform 1.5.7.
Directory traversal
HashiCorp Terraform Enterprise releases up to v202106-1 did not properly perform authorization checks on a subset of API requests executed using the run token
CVE-2021-36230
8.8 - High
- July 20, 2021
HashiCorp Terraform Enterprise releases up to v202106-1 did not properly perform authorization checks on a subset of API requests executed using the run token, allowing privilege escalation to organization owner. Fixed in v202107-1.
AuthZ
When using the Azure backend with a shared access signature (SAS)
CVE-2019-19316
7.5 - High
- December 02, 2019
When using the Azure backend with a shared access signature (SAS), Terraform versions prior to 0.12.17 may transmit the token and state snapshot using cleartext HTTP.
Use of a Broken or Risky Cryptographic Algorithm
aws/resource_aws_iam_user_login_profile.go in the HashiCorp Terraform Amazon Web Services (AWS) provider through v1.12.0 has an inappropriate PRNG algorithm and seeding, which makes it easier for remote attackers to obtain access by leveraging an IAM account
CVE-2018-9057
9.8 - Critical
- March 27, 2018
aws/resource_aws_iam_user_login_profile.go in the HashiCorp Terraform Amazon Web Services (AWS) provider through v1.12.0 has an inappropriate PRNG algorithm and seeding, which makes it easier for remote attackers to obtain access by leveraging an IAM account that was provisioned with a weak password.
Insufficient Entropy in PRNG
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for HashiCorp Terraform or by HashiCorp? Click the Watch button to subscribe.
