Vulnerabilities in pkg:nuget/Amazon.Extensions.S3.Encryption

PACKAGE
Advisory Identifier: GHSA-4v42-65r3-3gjx
Advisory Summary

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

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:nuget/Amazon.Extensions.S3.Encryption

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:nuget/Amazon.Extensions.S3.Encryption. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-4v42-65r3-3gjx CVE-2025-14759 MODERATE Amazon S3 Encryption Client for .NET has a Key Commitment Issue

CVE-2025-14759 at a Glance

CVE Identifier CVE-2025-14759
GHSA Identifier GHSA-4v42-65r3-3gjx
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-327: Use of a Broken or Risky Cryptographic Algorithm
Affected Product Amazon.Extensions.S3.Encryption
Package Ecosystem NuGet
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-14759

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

Amazon.Extensions.S3.Encryption fixed: 3.2.0
Upgrade Amazon.Extensions.S3.Encryption to 3.2.0
Verify Direct and Transitive Dependencies

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

inspect dependencies for Amazon.Extensions.S3.Encryption

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-14759, inspect your project dependencies for Amazon.Extensions.S3.Encryption:

inspect dependencies for Amazon.Extensions.S3.Encryption

Analyze the terminal output to locate any version of Amazon.Extensions.S3.Encryption in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.2.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

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.Extensions.S3.Encryption, 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 .NET (S3EC) 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 can 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: <= 3.1.0 ## Patches Amazon 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, the fix will be released 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, Amazon S3 Encryption Client asks that they contact AWS Security via the 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-14759 Affected Amazon.Extensions.S3.Encryption Versions

1 component(s)
Fixed Versions:
3.2.0
Product / Package Ecosystem Affected Versions Fixed Version
Amazon.Extensions.S3.Encryption
NuGet
< 3.2.0
3.2.0

References

Frequently Asked Questions

What is CVE-2025-14759?
CVE-2025-14759 is a security vulnerability in Amazon.Extensions.S3.Encryption involving Amazon S3 Encryption Client for .NET has a Key Commitment Issue under CWE-327: Use of a Broken or Risky Cryptographic Algorithm.
Which Amazon.Extensions.S3.Encryption versions are affected?
Affected versions include releases prior to 3.2.0 across affected packages: Amazon.Extensions.S3.Encryption.
What version fixes CVE-2025-14759?
Upgrading to 3.2.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is Amazon.Extensions.S3.Encryption affected?
Yes, Amazon.Extensions.S3.Encryption is affected in releases prior to 3.2.0. Upgrade your dependency to 3.2.0 or later.
What is the CVSS score of CVE-2025-14759?
CVE-2025-14759 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-14759?
CVE-2025-14759 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 NuGet dependencies for CVE-2025-14759?
Run the dependency tree command: 'inspect dependencies for Amazon.Extensions.S3.Encryption'. 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-4v42-65r3-3gjx",
  "modified" : "2025-12-18T15:46:16Z",
  "published" : "2025-12-18T15:46:16Z",
  "aliases" : [ "CVE-2025-14759" ],
  "summary" : "Amazon S3 Encryption Client for .NET has a Key Commitment Issue",
  "details" : "## Summary\n\nS3 Encryption Client for .NET (S3EC) 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\n## Impact\n\n### Background - Key Commitment\n\nThere is a cryptographic property whereby under certain conditions, a single ciphertext can 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: <= 3.1.0\n\n\n\n## Patches\n\nAmazon 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, the fix will be released 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\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, Amazon S3 Encryption Client asks that they contact AWS Security via the 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" : "NuGet",
      "name" : "Amazon.Extensions.S3.Encryption"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.2.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/aws/amazon-s3-encryption-client-dotnet/security/advisories/GHSA-4v42-65r3-3gjx"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-14759"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/aws/amazon-s3-encryption-client-dotnet/commit/6a0272c79347b2672eea599f73ee1a94d131e899"
  }, {
    "type" : "WEB",
    "url" : "https://aws.amazon.com/security/security-bulletins/AWS-2025-032"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/aws/amazon-s3-encryption-client-dotnet"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/aws/amazon-s3-encryption-client-dotnet/releases/tag/release_2025-12-17"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-327" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-12-18T15:46:16Z",
    "nvd_published_at" : "2025-12-17T20:15:52Z"
  }
}