CVE-2025-14763: CWE-327: Use of a Broken or Risky Cryptographic Algorithm in AWS S3 Encryption Client for Java
Bulletin ID: AWS-2025-032 Scope: AWS Content Type: Important (requires attention) Publication Date: 2025/12/17 12:15 PM PST We identify the following CVEs: CVE-2025-14763 - Key Commitment Issues in S3 Encryption Client in Java CVE-2025-14764 - Key Commitment Issues in S3 Encryption Client in Go CVE-2025-14759 - Key Commitment Issues in S3 Encryption Client in .NET CVE-2025-14760 - Key Commitment Issues in S3 Encryption Client in C++ - part of the AWS SDK for C++ CVE-2025-14761 - Key Commitment Issues in S3 Encryption Client in PHP - part of the AWS SDK for PHP CVE-2025-14762 - Key Commitment Issues in S3 Encryption Client in Ruby - part of the AWS SDK for Ruby Description: S3 Encryption Clients for Java, Go, .NET, C++, PHP, and Ruby are open-source client-side encryption libraries used to facilitate writing and reading encrypted records to S3. When the encrypted data key (EDK) is stored in an "Instruction File" instead of S3's metadata record, the EDK is exposed to an "Invisible Salamanders" attack, which could allow the EDK to be replaced with a new key. Resolution: - S3 Encryption Client Java: <= 3.5.0 - S3 Encryption Client Go: <= 3.1.0 - S3 Encryption Client .NET: <= 3.1 - AWS SDK for C++: <= 1.11.711 - AWS SDK for PHP: <= 3.367.0 - AWS SDK for Ruby: <= 1.207.0
AI Analysis
Technical Summary
CVE-2025-14763 is a vulnerability in the AWS S3 Encryption Client for Java involving the use of a broken or risky cryptographic algorithm due to missing cryptographic key commitment. This allows an attacker with write access to an S3 bucket to insert a manipulated encrypted data key (EDK) that decrypts to altered plaintext when stored in an instruction file instead of S3 metadata. The issue affects data integrity but does not compromise confidentiality or availability. Exploitation requires network access and low privileges, with no user interaction. AWS has addressed this vulnerability in version 4.0.0 or later of the client.
Potential Impact
The vulnerability impacts data integrity by allowing an attacker with write access to manipulate encrypted data keys, potentially causing decrypted data to differ from the original. Confidentiality and availability of data are not affected. There is no evidence of exploitation in the wild. The attack requires network access and low privileges, making it feasible in environments where write permissions to S3 buckets are not properly restricted.
Mitigation Recommendations
AWS has fixed this vulnerability in version 4.0.0 or later of the S3 Encryption Client for Java. Organizations should upgrade to this fixed version promptly. Additionally, it is recommended to audit and restrict S3 bucket write permissions to minimize the risk of exploitation. Patch status is confirmed by the vendor advisory indicating an official fix is available.
Affected Countries
Germany, United Kingdom, France, Netherlands
CVE-2025-14763: CWE-327: Use of a Broken or Risky Cryptographic Algorithm in AWS S3 Encryption Client for Java
Description
Bulletin ID: AWS-2025-032 Scope: AWS Content Type: Important (requires attention) Publication Date: 2025/12/17 12:15 PM PST We identify the following CVEs: CVE-2025-14763 - Key Commitment Issues in S3 Encryption Client in Java CVE-2025-14764 - Key Commitment Issues in S3 Encryption Client in Go CVE-2025-14759 - Key Commitment Issues in S3 Encryption Client in .NET CVE-2025-14760 - Key Commitment Issues in S3 Encryption Client in C++ - part of the AWS SDK for C++ CVE-2025-14761 - Key Commitment Issues in S3 Encryption Client in PHP - part of the AWS SDK for PHP CVE-2025-14762 - Key Commitment Issues in S3 Encryption Client in Ruby - part of the AWS SDK for Ruby Description: S3 Encryption Clients for Java, Go, .NET, C++, PHP, and Ruby are open-source client-side encryption libraries used to facilitate writing and reading encrypted records to S3. When the encrypted data key (EDK) is stored in an "Instruction File" instead of S3's metadata record, the EDK is exposed to an "Invisible Salamanders" attack, which could allow the EDK to be replaced with a new key. Resolution: - S3 Encryption Client Java: <= 3.5.0 - S3 Encryption Client Go: <= 3.1.0 - S3 Encryption Client .NET: <= 3.1 - AWS SDK for C++: <= 1.11.711 - AWS SDK for PHP: <= 3.367.0 - AWS SDK for Ruby: <= 1.207.0
CVSS v3.1
Score 5.3medium
Affected software
pkg:maven/com.amazonaws/amazon-s3-encryption-clientRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-14763 is a vulnerability in the AWS S3 Encryption Client for Java involving the use of a broken or risky cryptographic algorithm due to missing cryptographic key commitment. This allows an attacker with write access to an S3 bucket to insert a manipulated encrypted data key (EDK) that decrypts to altered plaintext when stored in an instruction file instead of S3 metadata. The issue affects data integrity but does not compromise confidentiality or availability. Exploitation requires network access and low privileges, with no user interaction. AWS has addressed this vulnerability in version 4.0.0 or later of the client.
Potential Impact
The vulnerability impacts data integrity by allowing an attacker with write access to manipulate encrypted data keys, potentially causing decrypted data to differ from the original. Confidentiality and availability of data are not affected. There is no evidence of exploitation in the wild. The attack requires network access and low privileges, making it feasible in environments where write permissions to S3 buckets are not properly restricted.
Mitigation Recommendations
AWS has fixed this vulnerability in version 4.0.0 or later of the S3 Encryption Client for Java. Organizations should upgrade to this fixed version promptly. Additionally, it is recommended to audit and restrict S3 bucket write permissions to minimize the risk of exploitation. Patch status is confirmed by the vendor advisory indicating an official fix is available.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- AMZN
- Date Reserved
- 2025-12-16T00:24:32.968Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6943126ec9138a40d2ed325a
Added to database: 12/17/2025, 20:28:30 UTC
Last enriched: 06/05/2026, 19:29:45 UTC
Last updated: 08/19/2026, 22:52:06 UTC
Views: 335
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.