CVE-2018-9057

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 36% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
78.8%
KEV
Not listed

Published

March 27, 2018

Last Modified

November 21, 2024

Advisory Details (1)

Auto-updated Jun 6, 2026
No patch confirmed yet. Sources: github_pr.
github_pr

Fix password generation in resourceAwsIamUserLoginProfile

Upstream fix in progress (PR #3934 · terraform-providers/terraform-provider-aws, state=closed)

https://github.com/terraform-providers/terraform-provider-aws/pull/3934

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/hashicorp/terraform-provider-aws—1.14.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-12 05:43 UTCEPSS rescore
  2. 2026-07-09 19:06 UTCEPSS rescore
  3. 2026-07-08 15:11 UTCEPSS rescore
  4. 2026-07-08 15:11 UTCEPSS rescore
  5. 2026-07-07 13:42 UTCEPSS rescore
  6. 2026-07-07 13:42 UTCEPSS rescore
  7. 2026-07-06 16:25 UTCEPSS rescore
  8. 2026-07-06 16:24 UTCEPSS rescore
  9. 2026-07-06 02:20 UTCEPSS rescore
  10. 2026-07-05 02:27 UTCEPSS rescore
  11. 2026-07-04 11:26 UTCOSV refresh
  12. 2026-07-04 06:28 UTCEPSS rescore
  13. 2026-07-04 06:28 UTCEPSS rescore
  14. 2026-07-01 15:03 UTCEPSS rescore
  15. 2026-07-01 15:03 UTCEPSS rescore
  16. 2026-06-30 23:20 UTCEPSS rescore
  17. 2026-06-30 23:20 UTCEPSS rescore
  18. 2026-06-28 14:04 UTCEPSS rescore
  19. 2026-06-28 04:53 UTCEPSS rescore
  20. 2026-06-28 04:53 UTCEPSS rescore
  21. 2026-06-27 03:06 UTCEPSS rescore
  22. 2026-06-27 03:06 UTCEPSS rescore
  23. 2026-06-25 13:47 UTCEPSS rescore
  24. 2026-06-25 13:47 UTCEPSS rescore
  25. 2026-06-24 14:02 UTCEPSS rescore
Show 52 more
  1. 2026-06-24 14:02 UTCEPSS rescore
  2. 2026-06-23 21:30 UTCEPSS rescore
  3. 2026-06-23 21:30 UTCEPSS rescore
  4. 2026-06-21 14:54 UTCEPSS rescore
  5. 2026-06-21 14:54 UTCEPSS rescore
  6. 2026-06-21 01:57 UTCEPSS rescore
  7. 2026-06-21 01:57 UTCEPSS rescore
  8. 2026-06-19 19:23 UTCEPSS rescore
  9. 2026-06-19 19:23 UTCEPSS rescore
  10. 2026-06-18 17:50 UTCEPSS rescore
  11. 2026-06-18 17:50 UTCEPSS rescore
  12. 2026-06-17 17:50 UTCEPSS rescore
  13. 2026-06-16 17:50 UTCEPSS rescore
  14. 2026-06-16 17:50 UTCEPSS rescore
  15. 2026-06-15 23:09 UTCOSV refresh
  16. 2026-06-15 17:45 UTCEPSS rescore
  17. 2026-06-14 23:15 UTCEPSS rescore
  18. 2026-06-14 23:15 UTCEPSS rescore
  19. 2026-06-13 22:58 UTCEPSS rescore
  20. 2026-06-12 23:09 UTCEPSS rescore
  21. 2026-06-12 23:09 UTCEPSS rescore
  22. 2026-06-11 13:57 UTCEPSS rescore
  23. 2026-06-10 22:16 UTCEPSS rescore
  24. 2026-06-10 13:19 UTCEPSS rescore
  25. 2026-06-08 14:14 UTCEPSS rescore
  26. 2026-06-07 15:22 UTCEPSS rescore
  27. 2026-06-07 15:22 UTCEPSS rescore
  28. 2026-06-06 13:45 UTCEPSS rescore
  29. 2026-06-06 13:45 UTCEPSS rescore
  30. 2026-06-05 22:45 UTCEPSS rescore
  31. 2026-06-05 22:45 UTCEPSS rescore
  32. 2026-06-05 06:08 UTCEPSS rescore
  33. 2026-06-05 06:08 UTCEPSS rescore
  34. 2026-06-04 13:10 UTCEPSS rescore
  35. 2026-06-04 13:10 UTCEPSS rescore
  36. 2026-06-02 20:11 UTCEPSS rescore
  37. 2026-06-01 13:50 UTCEPSS rescore
  38. 2026-05-31 22:29 UTCEPSS rescore
  39. 2026-05-31 22:29 UTCEPSS rescore
  40. 2026-05-31 00:14 UTCEPSS rescore
  41. 2026-05-31 00:14 UTCEPSS rescore
  42. 2026-05-29 13:41 UTCEPSS rescore
  43. 2026-05-28 13:43 UTCEPSS rescore
  44. 2026-05-28 13:42 UTCEPSS rescore
  45. 2026-05-28 09:58 UTCEG score recompute
  46. 2026-05-28 09:58 UTCVendor advisory
  47. 2026-05-28 03:33 UTCOSV refresh
  48. 2026-05-27 13:38 UTCEPSS rescore
  49. 2026-05-26 13:42 UTCEPSS rescore
  50. 2026-05-26 13:42 UTCEPSS rescore
  51. 2026-05-26 07:17 UTCEPSS rescore
  52. 2026-05-26 07:17 UTCEPSS rescore

Frequently asked(5)

What is CVE-2018-9057?
CVE-2018-9057 is a critical vulnerability published on March 27, 2018. aws/resourceawsiamuserlogin_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.
When was CVE-2018-9057 disclosed?
CVE-2018-9057 was first published in the National Vulnerability Database on March 27, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-9057 actively exploited?
CVE-2018-9057 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 78.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-9057?
CVE-2018-9057 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2018-9057?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-9057, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-9057

Explore →

Is Your Infrastructure Affected by CVE-2018-9057?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs