Home

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.

PUBLISHED Reserved 2025-12-16 | Published 2025-12-17 | Updated 2025-12-17 | Assigner AMZN




MEDIUM: 5.3CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N

MEDIUM: 6.0CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Problem types

CWE-327: Use of a Broken or Risky Cryptographic Algorithm

Product status

Default status
unaffected

4.0.0
unaffected

References

aws.amazon.com/security/security-bulletins/AWS-2025-032/ vendor-advisory

github.com/...t-java/security/advisories/GHSA-x44p-gvrj-pj2r third-party-advisory

github.com/...-s3-encryption-client-java/releases/tag/v4.0.0 patch

cve.org (CVE-2025-14763)

nvd.nist.gov (CVE-2025-14763)

Download JSON

Data based on CVE®. Copyright © 1999-2025, The MITRE Corporation. All rights reserved.