Security readout for executives and security teams
Plain-English summary
Terraform AWS provider versions through v1.12.0 could generate weak IAM user login-profile passwords because of inappropriate random number generation and seeding. The business risk is unauthorized AWS console access to affected IAM accounts if those generated passwords were still in use.
Executive priority
Treat as a credential hygiene issue with potentially high impact if affected IAM users remain active. Prioritize discovery and password rotation over broad emergency response unless logs show suspicious access.
Technical view
The issue is in aws/resource_aws_iam_user_login_profile.go in the HashiCorp Terraform AWS provider through v1.12.0. Weak PRNG behavior made generated IAM login-profile passwords easier to predict or obtain. No CVSS, CWE, or patched version details are provided in the source bundle.
Likely exposure
Exposure is likely limited to AWS IAM user login profiles provisioned by Terraform AWS provider v1.12.0 or earlier. Risk may persist after upgrades if generated passwords were never rotated.
Exploitation context
The bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVE describes possible remote attacker access by leveraging an IAM account provisioned with a weak password.
Researcher notes
The public metadata lacks CVSS, CWE, and explicit fixed-version details. Analysis should stay scoped to Terraform AWS provider generated IAM login-profile passwords through v1.12.0 and avoid assuming all Terraform-managed AWS resources are affected.
Mitigation direction
- Identify Terraform AWS provider usage at v1.12.0 or earlier.
- Rotate IAM console passwords for affected login-profile users.
- Upgrade the Terraform AWS provider according to vendor guidance.
- Review IAM users for unnecessary console login access.
- Enforce MFA and least privilege for IAM users.
Validation and detection
- Search Terraform state and code for aws_iam_user_login_profile resources.
- Confirm historical provider versions used to provision IAM login profiles.
- Check whether generated IAM passwords were rotated after provisioning.
- Audit AWS IAM users with console password enabled.
- Review AWS logs for suspicious console authentication activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Credential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2018-9057 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/terraform-providers/terraform-provider-aws/pull/3934CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.