CVE-2025-14763: Amazon s3 encryption client java Amazon S3 Encryption Client For Vulnerability

MODERATE
Advisory Identifier: GHSA-x44p-gvrj-pj2r
CVSS 5.3
CWE-327
Published
Advisory Summary

CVE-2025-14763 is a MODERATE (CVSS 5.3) amazon s3 encryption client for vulnerability (CWE-327: Use of a Broken or Risky Cryptographic Algorithm) affecting Amazon s3 encryption client java libraries in the Maven ecosystem. The issue involves amazon s3 encryption client for java has a key commitment issue. Remediation is available by upgrading affected packages to version 4.0.0.

CVE-2025-14763 at a Glance

CVE Identifier CVE-2025-14763
GHSA Identifier GHSA-x44p-gvrj-pj2r
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-327: Use of a Broken or Risky Cryptographic Algorithm
Affected Product Amazon s3 encryption client java
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2025-14763

To remediate this vulnerability, upgrade all affected Amazon s3 encryption client java dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

software.amazon.encryption.s3:amazon-s3-encryption-client-java fixed: 4.0.0
<dependency>
    <groupId>software.amazon.encryption.s3</groupId>
    <artifactId>amazon-s3-encryption-client-java</artifactId>
    <version>4.0.0</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=software.amazon.encryption.s3

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2025-14763, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=software.amazon.encryption.s3

Analyze the terminal output to locate any version of Amazon s3 encryption client java in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.0.0), your application is affected.

Note: The mvn dependency:tree -Dincludes=software.amazon.encryption.s3 command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-327: Use of a Broken or Risky Cryptographic Algorithm, where the product uses a broken or risky cryptographic algorithm or protocol. In Amazon s3 encryption client java, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary S3 Encryption Client for Java is an open-source client-side encryption library 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 (https://eprint.iacr.org/2019/016), which could allow the EDK to be replaced with a new key. ## Impact ### Background - Key Commitment There is a cryptographic property whereby under certain conditions, a single ciphertext could be decrypted into 2 different plaintexts by using different encryption keys. To address this issue, strong encryption schemes use what is known as "key commitment", a process by which an encrypted message can only be decrypted by one key; the key used to originally encrypt the message. In older versions of S3EC, when customers are also using a feature called "Instruction File" to store EDKs, key commitment is not implemented because multiple EDKs could be associated to an underlying encrypted message object. For such customers an attack that leverages the lack of key commitment is possible. A bad actor would need two things to leverage this issue: (i) the ability to create a separate, rogue, EDK that will also decrypt the underlying object to produce desired plaintext, and (ii) permission to upload a new instruction file to the S3 bucket to replace the existing instruction file placed there by the user using the S3C. Any future attempt to decrypt the underlying encrypted message with the S3EC will unwittingly use the rogue EDK to produce a valid plaintext message. Impacted versions: <= v3.5 ## Patches S3 Encryption Client is introducing the concept of "key commitment" to S3EC where the EDK is cryptographically bound to the ciphertext in order to address this issue. In order to maintain compatibility for in-flight messages we are releasing the fix in two versions. A code-compatible minor version that can read messages with key-commitment but not write them, and a new major version that can both read and write messages with key-commitment. For maximum safety customers are asked to upgrade to the latest major version: 4.0.0 or later ## Workarounds There are no workarounds, please upgrade to the suggested version of S3EC. ## References If users have any questions or comments about this advisory, S3 Encryption Client asks that they contact AWS Security via our issue reporting page or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.

CVE-2025-14763 Affected Amazon s3 encryption client java Versions

1 component(s)
Fixed Versions:
4.0.0
Product / Package Ecosystem Affected Versions Fixed Version
software.amazon.encryption.s3:amazon-s3-encryption-client-java
Maven
< 4.0.0
4.0.0

References

Frequently Asked Questions

What is CVE-2025-14763?
CVE-2025-14763 is a security vulnerability in Amazon s3 encryption client java involving Amazon S3 Encryption Client for Java has a Key Commitment Issue under CWE-327: Use of a Broken or Risky Cryptographic Algorithm.
Which Amazon s3 encryption client java versions are affected?
Affected versions include releases prior to 4.0.0 across affected packages: software.amazon.encryption.s3:amazon-s3-encryption-client-java.
What version fixes CVE-2025-14763?
Upgrading to 4.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is amazon-s3-encryption-client-java affected?
Yes, software.amazon.encryption.s3:amazon-s3-encryption-client-java is affected in releases prior to 4.0.0. Upgrade your dependency to 4.0.0 or later.
What is the CVSS score of CVE-2025-14763?
CVE-2025-14763 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N.
What CWE is associated with CVE-2025-14763?
CVE-2025-14763 is classified under CWE-327: Use of a Broken or Risky Cryptographic Algorithm (The product uses a broken or risky cryptographic algorithm or protocol.).
How can I check Maven dependencies for CVE-2025-14763?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=software.amazon.encryption.s3'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-x44p-gvrj-pj2r",
  "modified" : "2025-12-18T15:47:07Z",
  "published" : "2025-12-18T15:47:07Z",
  "aliases" : [ "CVE-2025-14763" ],
  "summary" : "Amazon S3 Encryption Client for Java has a Key Commitment Issue",
  "details" : "## Summary\n\nS3 Encryption Client for Java is an open-source client-side encryption library used to facilitate writing and reading encrypted records to S3.  \n\nWhen 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  (https://eprint.iacr.org/2019/016), which could allow the EDK to be replaced with a new key. \n\n\n## Impact\n\n### Background - Key Commitment\n\nThere is a cryptographic property whereby under certain conditions, a single ciphertext could be decrypted into 2 different plaintexts by using different encryption keys. To address this issue, strong encryption schemes use what is known as \"key commitment\", a process by which an encrypted message can only be decrypted by one key; the key used to originally encrypt the message. \n\nIn older versions of S3EC, when customers are also using a feature called \"Instruction File\" to store EDKs, key commitment is not implemented because multiple EDKs could be associated to an underlying encrypted message object. For such customers an attack that leverages the lack of key commitment is possible. A bad actor would need two things to leverage this issue: (i) the ability to create a separate, rogue, EDK that will also decrypt the underlying object to produce desired plaintext, and (ii) permission to upload a new instruction file to the S3 bucket to replace the existing instruction file placed there by the user using the S3C.  Any future attempt to decrypt the underlying encrypted message with the S3EC will unwittingly use the rogue EDK to produce a valid plaintext message.\n\nImpacted versions: <= v3.5\n\n## Patches\n\nS3 Encryption Client is introducing the concept of \"key commitment\" to S3EC where the EDK is cryptographically bound to the ciphertext in order to address this issue. In order to maintain compatibility for in-flight messages we are releasing the fix in two versions.  A code-compatible minor version that can read messages with key-commitment but not write them, and a new major version that can both read and write messages with key-commitment. For maximum safety customers are asked to upgrade to the latest major version: 4.0.0 or later\n\n## Workarounds\n\nThere are no workarounds, please upgrade to the suggested version of S3EC.\n\n## References\n\nIf users have any questions or comments about this advisory, S3 Encryption Client asks that they contact AWS Security via our issue reporting page or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "software.amazon.encryption.s3:amazon-s3-encryption-client-java"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/aws/amazon-s3-encryption-client-java/security/advisories/GHSA-x44p-gvrj-pj2r"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-14763"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/aws/amazon-s3-encryption-client-java/commit/9d4523edbbc249781b3b3b3f8868fad39c5673d5"
  }, {
    "type" : "WEB",
    "url" : "https://aws.amazon.com/security/security-bulletins/AWS-2025-032"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/aws/amazon-s3-encryption-client-java"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/aws/amazon-s3-encryption-client-java/releases/tag/v4.0.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-327" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-12-18T15:47:07Z",
    "nvd_published_at" : "2025-12-17T21:15:53Z"
  }
}