Advisory Database
  • Advisories
  • Dependency Scanning
  1. maven
  2. ›
  3. com.amazonaws/aws-dynamodb-encryption-java
  4. ›
  5. GMS-2021-59

GMS-2021-59: Key Caching behavior in the DynamoDB Encryption Client.

February 8, 2021

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.

References

  • github.com/advisories/GHSA-w736-hf9p-qqh3
  • github.com/aws/aws-dynamodb-encryption-java/blob/master/CHANGELOG.md
  • github.com/aws/aws-dynamodb-encryption-java/commit/7de5f5a5929271ab25bce685089eb7ec564dac4b
  • github.com/aws/aws-dynamodb-encryption-java/security/advisories/GHSA-w736-hf9p-qqh3

Code Behaviors & Features

Detect and mitigate GMS-2021-59 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 1.15.0

Fixed versions

  • 1.15.0

Solution

Upgrade to version 1.15.0 or above.

Source file

maven/com.amazonaws/aws-dynamodb-encryption-java/GMS-2021-59.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Wed, 14 May 2025 12:15:45 +0000.