Vulnerabilities in pkg:maven/com.amazonaws/aws-dynamodb-encryption-java

PACKAGE
Advisory Summary

GHSA-w736-hf9p-qqh3 is a LOW key caching behavior vulnerability (CWE-862: Missing Authorization) affecting Aws dynamodb encryption java libraries in the Maven ecosystem. The issue involves key caching behavior in the dynamodb encryption client.. Remediation is available by upgrading affected packages to version 1.15.0.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:maven/com.amazonaws/aws-dynamodb-encryption-java

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:maven/com.amazonaws/aws-dynamodb-encryption-java. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-w736-hf9p-qqh3 - LOW Key Caching behavior in the DynamoDB Encryption Client.

GHSA-w736-hf9p-qqh3 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-w736-hf9p-qqh3
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-862: Missing Authorization
Affected Product Aws dynamodb encryption java
Package Ecosystem Maven
Published Date
Last Updated

How to Fix GHSA-w736-hf9p-qqh3

To remediate this vulnerability, upgrade all affected Aws dynamodb encryption 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.

com.amazonaws:aws-dynamodb-encryption-java fixed: 1.15.0
<dependency>
    <groupId>com.amazonaws</groupId>
    <artifactId>aws-dynamodb-encryption-java</artifactId>
    <version>1.15.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=com.amazonaws

How to Check if You Are Affected

To determine whether your Java application is affected by GHSA-w736-hf9p-qqh3, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=com.amazonaws

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

Note: The mvn dependency:tree -Dincludes=com.amazonaws 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-862: Missing Authorization, where the product does not perform an authorization check when an actor attempts to access a resource or perform an action. In Aws dynamodb encryption 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

### Impact This advisory concerns users of MostRecentProvider in the DynamoDB Encryption Client with a key provider like AWS Key Management Service that allows for permissions on keys to be modified. When key usage permissions were changed at the key provider, time-based key reauthorization logic in MostRecentProvider did not reauthorize the use of the key. This created the potential for keys to be used in the DynamoDB Encryption Client after permissions to do so were revoked at the key provider. ### Patches Fixed as of 1.15.0. We recommend users to modify their code and adopt `CachingMostRecentProvider`. ### Workarounds Users who cannot upgrade to use the `CachingMostRecentProvider` can call `clear()` on the cache to manually flush all of its contents. Next use of the key will force a re-validation to occur with the key provider.

GHSA-w736-hf9p-qqh3 Affected Aws dynamodb encryption java Versions

1 component(s)
Fixed Versions:
1.15.0
Product / Package Ecosystem Affected Versions Fixed Version
com.amazonaws:aws-dynamodb-encryption-java
Maven
< 1.15.0
1.15.0

References

Frequently Asked Questions

What is GHSA-w736-hf9p-qqh3?
GHSA-w736-hf9p-qqh3 is a security vulnerability in Aws dynamodb encryption java involving Key Caching behavior in the DynamoDB Encryption Client. under CWE-862: Missing Authorization.
Which Aws dynamodb encryption java versions are affected?
Affected versions include releases prior to 1.15.0 across affected packages: com.amazonaws:aws-dynamodb-encryption-java.
What version fixes GHSA-w736-hf9p-qqh3?
Upgrading to 1.15.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is aws-dynamodb-encryption-java affected?
Yes, com.amazonaws:aws-dynamodb-encryption-java is affected in releases prior to 1.15.0. Upgrade your dependency to 1.15.0 or later.
What CWE is associated with GHSA-w736-hf9p-qqh3?
GHSA-w736-hf9p-qqh3 is classified under CWE-862: Missing Authorization (The product does not perform an authorization check when an actor attempts to access a resource or perform an action.).
How can I check Maven dependencies for GHSA-w736-hf9p-qqh3?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=com.amazonaws'. 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-w736-hf9p-qqh3",
  "modified" : "2021-02-05T21:21:40Z",
  "published" : "2021-02-08T17:43:36Z",
  "aliases" : [ ],
  "summary" : "Key Caching behavior in the DynamoDB Encryption Client.",
  "details" : "### Impact\nThis advisory concerns users of MostRecentProvider in the DynamoDB Encryption Client with a key provider like AWS Key Management Service that allows for permissions on keys to be modified.\n\nWhen key usage permissions were changed at the key provider, time-based key reauthorization logic in MostRecentProvider did not reauthorize the use of the key. This created the potential for keys to be used in the DynamoDB Encryption Client after permissions to do so were revoked at the key provider.\n\n### Patches\nFixed as of 1.15.0.  We recommend users to modify their code and adopt `CachingMostRecentProvider`.\n\n### Workarounds\nUsers who cannot upgrade to use the `CachingMostRecentProvider` can call `clear()` on the cache to manually flush all of its contents. Next use of the key will force a re-validation to occur with the key provider.",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "com.amazonaws:aws-dynamodb-encryption-java"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.15.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/aws/aws-dynamodb-encryption-java/security/advisories/GHSA-w736-hf9p-qqh3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/aws/aws-dynamodb-encryption-java/commit/7de5f5a5929271ab25bce685089eb7ec564dac4b"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/aws/aws-dynamodb-encryption-java/blob/master/CHANGELOG.md#1150----2021-02-04"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-862" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-02-05T21:21:40Z",
    "nvd_published_at" : null
  }
}