-
Notifications
You must be signed in to change notification settings - Fork 148
Closed
Labels
area/securityMarks an issue as improving security of the projectMarks an issue as improving security of the projectkind/issueUnidentified issue, it could be a bug, misconfig, or anything in betweenUnidentified issue, it could be a bug, misconfig, or anything in betweenpossibly-outdatedFor github issues over a year oldFor github issues over a year old
Description
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:
Line 15 in 18d1893
| 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:
- https://security.googleblog.com/2023/04/supply-chain-security-for-go-part-1.html
- https://osv.dev/vulnerability/GO-2022-0646
- x/vulndb: suggestion regarding <GO-2022-0646> golang/vulndb#2350
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:
Metadata
Metadata
Assignees
Labels
area/securityMarks an issue as improving security of the projectMarks an issue as improving security of the projectkind/issueUnidentified issue, it could be a bug, misconfig, or anything in betweenUnidentified issue, it could be a bug, misconfig, or anything in betweenpossibly-outdatedFor github issues over a year oldFor github issues over a year old