GitHub Advisoryadvisory · Maven
GHSA-w736-hf9p-qqh3 Key Caching behavior in the DynamoDB Encryption Client.
LOW
Official page ↗
- Ecosystem
- Maven
- Packages
- com.amazonaws:aws-dynamodb-encryption-java
- Severity
- Low
- Weaknesses
- CWE-862
- Reviewed
- 2021-02-05
Affected packages
• Maven com.amazonaws:aws-dynamodb-encryption-java: < 1.15.0 → fixed in 1.15.0
Description
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.
Related
Weakness · CWE (1)
- CWE-862 Missing Authorization weakness