Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

x/vulndb: potential Go vuln in github.com/terraform-providers/terraform-provider-aws: CVE-2018-9057 #2220

Closed
tatianab opened this issue Nov 8, 2023 · 2 comments
Closed

x/vulndb: potential Go vuln in github.com/terraform-providers/terraform-provider-aws: CVE-2018-9057 #2220

tatianab opened this issue Nov 8, 2023 · 2 comments
Labels
excluded: LEGACY_FALSE_POSITIVE (DO NOT USE) Vulnerability marked as false positive before we introduced the triage process

Comments

@tatianab
Copy link
Contributor

tatianab commented Nov 8, 2023

CVE-2018-9057 references github.com/terraform-providers/terraform-provider-aws, which may be a Go module.

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.

References:

Cross references:
No existing reports found with this module or alias.

See doc/triage.md for instructions on how to triage this report.

modules:
    - module: github.com/terraform-providers/terraform-provider-aws
      vulnerable_at: 1.60.0
      packages:
        - package: n/a
cves:
    - CVE-2018-9057
references:
    - fix: https://github.com/terraform-providers/terraform-provider-aws/pull/3934
@tatianab tatianab added the excluded: LEGACY_FALSE_POSITIVE (DO NOT USE) Vulnerability marked as false positive before we introduced the triage process label Nov 8, 2023
@gopherbot
Copy link
Contributor

Change https://go.dev/cl/540721 mentions this issue: data/excluded: batch add 135 excluded reports

@GoVulnBot GoVulnBot mentioned this issue Feb 22, 2024
Closed
@gopherbot
Copy link
Contributor

Change https://go.dev/cl/567835 mentions this issue: data/excluded: add missing alias for GO-2023-2220.yaml

gopherbot pushed a commit that referenced this issue Feb 28, 2024
@tatianab
data/excluded: add missing alias for GO-2023-2220.yaml
6d9e3e6 
Aliases: CVE-2018-9057, GHSA-r48h-jr2j-9g78

Updates #2220
Fixes #2577

Change-Id: Ieb2a54ee229c438c39c62fe7f1e6a5ebdf6b4515
Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/567835
Reviewed-by: Jonathan Amsterdam <jba@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
excluded: LEGACY_FALSE_POSITIVE (DO NOT USE) Vulnerability marked as false positive before we introduced the triage process
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tatianab @gopherbot