CVE-2018-9057 json
HashiCorp Terraform Amazon Web Services (AWS) uses an insecure PRNG
published 2018-03-27 8 y ago modified 2026-09-10 1 mo ago also GHSA-r48h-jr2j-9g78 , EUVD-2022-5084
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/hashicorp/terraform-provider-aws 1.14.0
Exploit prediction
1.92% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/hashicorp/terraform-provider-aws | <1.14.0 |
1.14.0 |
Classification
- Weakness
-
- CWE-332 Insufficient Entropy in PRNG
References
-
github.com
/terraform-providers/terraform-provider-aws/pull/3934
web, issue-tracking, patch, third-party-advisory
-
github.com
/hashicorp/terraform-provider-aws/pull/3934
web
-
github.com
/hashicorp/terraform-provider-aws/pull/3989
web
-
github.com
/hashicorp/terraform-provider-aws/commit/efa8cd45c6484ff70b2a515ea7ff06f2459d4ddf
web
-
nvd.nist.gov
/vuln/detail/CVE-2018-9057
advisory
-
github.com
/hashicorp/terraform-provider-aws
package
-
github.com
/hashicorp/terraform-provider-aws/blob/02b039aa82dd7fc6e4a97a0922cc5dbbab724021/resource_aws_iam_user_login_pr
web
Sources
- CVE List CVE-2018-9057
- GitHub Advisory GHSA-r48h-jr2j-9g78
- NVD CVE-2018-9057
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.