# CVE-2018-9057: HashiCorp Terraform Amazon Web Services (AWS) uses an insecure PRNG

> Weak password generation in Terraform AWS provider allows attackers to guess IAM login credentials and take over accounts.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r48h-jr2j-9g78

## What is CVE-2018-9057?

CVE-2018-9057 is a critical vulnerability in n/a, published on 27 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-332 (Insufficient Entropy in PRNG)

## Which versions are affected by CVE-2018-9057?

2 open source packages ship an affected version, including github.com/hashicorp/terraform-provider-aws. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/hashicorp/terraform-provider-aws` | Go | All versions | 1.14.0 |
| `github.com/hashicorp/terraform-provider-aws` | Go | All versions | 1.14.0 |

Products: Hashicorp Terraform.

## How do I fix CVE-2018-9057?

Upgrade github.com/hashicorp/terraform-provider-aws to 1.14.0 or later.

## Is CVE-2018-9057 being exploited?

There is no known exploitation of CVE-2018-9057 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-36230](https://insights.sbomify.com/CVE-2021-36230/): Missing authorization in n/a (high 8.8)
- [CVE-2019-19316](https://insights.sbomify.com/CVE-2019-19316/): Use of a Broken or Risky Cryptographic Algorithm in Terraform (high 7.5)
- [CVE-2023-4782](https://insights.sbomify.com/CVE-2023-4782/): Terraform Allows Arbitrary File Write During Init Operation (medium 6.3)
- [CVE-2025-13432](https://insights.sbomify.com/CVE-2025-13432/): Terraform Enterprise state versions can be created by users with specific permissions without sufficient write access (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-9057 and fix it if it is affected.

What it is: CVE-2018-9057 is a critical vulnerability in n/a, published on 27 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-9057 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/hashicorp/terraform-provider-aws (Go): affected all versions; fixed in 1.14.0
- github.com/hashicorp/terraform-provider-aws (Go): affected all versions; fixed in 1.14.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-9057/ (Markdown: https://insights.sbomify.com/CVE-2018-9057/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-9057
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-9057
- OSV: https://osv.dev/vulnerability/CVE-2018-9057

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-9057/
Summaries are generated and may contain mistakes; the official description above is the record.