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.

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

[ISSUE] Vulnerability GO-2022-0646 in AWS SDK Go #1371

Open
Tracked by #1
drodriguez-305 opened this issue Feb 27, 2024 · 2 comments
Open
Tracked by #1

[ISSUE] Vulnerability GO-2022-0646 in AWS SDK Go #1371

drodriguez-305 opened this issue Feb 27, 2024 · 2 comments
Assignees
Labels
area/security Marks an issue as improving security of the project kind/issue Unidentified issue, it could be a bug, misconfig, or anything in between

Comments

@drodriguez-305
Copy link
Contributor

Describe the issue:
We have identified a security vulnerability, referenced as GO-2022-0646, in our project that uses the AWS SDK for Go. This vulnerability arises from using the V1 EncryptionClient, specifically with AES-CBC content cipher or the KMS key wrap algorithm. An attacker with write access to an S3 bucket could potentially decrypt files in that bucket.

It can only be triggered, though, if a particular, deprecated function is called. We would need to confirm this.

How to reproduce:

github.com/aws/aws-sdk-go v1.44.122 // indirect

Possible Solutions/Workarounds:

  • Migrating from the V1 EncryptionClient to the V1 EncryptionClientV2 API in AWS SDK for Go as recommended.
  • Assessing the feasibility of updating our project to use AWS SDK for Go v2, which may offer more robust security features and is not affected by this vulnerability.
  • Confirm its a false positive by ensuring the deprecated function is not called.

Useful Links:

Environment:

Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.

  • AWS SDK for Go version: 1.44.122
  • Platform:
  • Helm CLI version:
  • Chart version:
  • Values file:
@drodriguez-305 drodriguez-305 added kind/issue Unidentified issue, it could be a bug, misconfig, or anything in between area/security Marks an issue as improving security of the project labels Feb 27, 2024
@drodriguez-305 drodriguez-305 self-assigned this Mar 6, 2024
@drodriguez-305
Copy link
Contributor Author

@aabouzaid

Can we remove this dependency as it is indirect?

@aabouzaid
Copy link
Member

@drodriguez-305 We cannot remove them since they are needed by the module we use github.com/gruntwork-io/terratest. I've checked the latest version and of terratest and I see that it uses the vulnerable version.

So let's ignore them as described in the remediation section using osv-scanner.toml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/security Marks an issue as improving security of the project kind/issue Unidentified issue, it could be a bug, misconfig, or anything in between
Projects
None yet
Development

No branches or pull requests

2 participants