dynamodb-encryption-sdk
Affected
- introduced
0, fixed1.3.0(ecosystem)
Fixed versions
1.3.0
Fix
- Fixed version
1.3.0pip install --upgrade dynamodb-encryption-sdk==1.3.0
Advisory
Also known as: None
Key Caching behavior in the DynamoDB Encryption Client.
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.3.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.
Low Basis: The source's own band: LOW
0, fixed 1.3.0 (ecosystem)1.3.0
1.3.0pip install --upgrade dynamodb-encryption-sdk==1.3.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0