Description
Missing cryptographic key commitment in the Amazon S3 Encryption Client for Java 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 Java to version 4.0.0 or later.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| AWS | S3 Encryption Client for Java | — | 4.0.0 |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Wolfi
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Wolfi rolling | apache-nifi-compat +1 | 2.7.2-r2 | — |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| Maven | software.amazon.encryption.s3:amazon-s3-encryption-client-java | < 4.0.0 | 4.0.0 | GHSA-x44p-gvrj-pj2r |