Amazon S3 Encryption Client has a Key Commitment Issue
AWS S3 Encryption Client for Go
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/aws/amazon-s3-encryption-client-go/v3 Go |
|
|
| github.com/aws/amazon-s3-encryption-client-go Go |
| No fix yet |
AWS S3 Encryption Client for Go
| Product | Affected | Fixed in |
|---|---|---|
| github.com/aws/amazon-s3-encryption-client-go/v3 Go |
|
|
| github.com/aws/amazon-s3-encryption-client-go Go |
| No fix yet |
|
|
Missing cryptographic key commitment in the Amazon S3 Encryption Client for Go may allow a user with write access to the S3 bucket to introduce a new EDK that decrypts to different plaintext when the encrypted data key is stored in an "instruction file" instead of S3's metadata record.
To mitigate this issue, upgrade Amazon S3 Encryption Client for Go to version 4.0 or later.
From the CVE record · AMZN
The client lacks cryptographic key commitment when an encrypted data key is stored in an instruction file rather than S3 metadata. A user with write access to the S3 bucket may introduce a new encrypted data key that decrypts to different plaintext.
Check users of github.com/aws/amazon-s3-encryption-client-go/v3 before 4.0.0, github.com/aws/amazon-s3-encryption-client-go/v4 before 4.0.0, and all versions of github.com/aws/amazon-s3-encryption-client-go.