dynamodb-encryption-sdk
DynamoDB Encryption Client for Python
Activity
- Latest release
- 2y ago
- Total releases
- 20
- Cadence
- ~41 days
- Last 12 months
- 0
Details
- License
- Apache-2.0
- First release
- May 02, 2018
| Version | Released | |
|---|---|---|
3.3.0
minor
| ||
3.2.0
minor
| ||
2.1.1
patch
| ||
1.3.1
patch
| ||
3.1.0
minor
| ||
3.0.0
major
| ||
2.1.0
minor
| ||
2.0.0
major
| ||
1.3.0
minor
| ||
1.2.0
minor
1 CVE
GHSA-4ph2-8337-hm62
Feb 08, 2021
Key Caching behavior in the DynamoDB Encryption Client.
Low
ImpactThis 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. PatchesFixed as of 1.3.0. We recommend users to modify their code and adopt WorkaroundsUsers who cannot upgrade to use the Affected versions
1.0.0
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.6
1.0.7
1.1.0
1.1.1
1.2.0
Fixed in
1.3.0
References
Updated Dec 02, 2024 · Source: OSV.dev | ||
1.1.1
patch
1 CVE
GHSA-4ph2-8337-hm62
Feb 08, 2021
Key Caching behavior in the DynamoDB Encryption Client.
Low
ImpactThis 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. PatchesFixed as of 1.3.0. We recommend users to modify their code and adopt WorkaroundsUsers who cannot upgrade to use the Affected versions
1.0.0
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.6
1.0.7
1.1.0
1.1.1
1.2.0
Fixed in
1.3.0
References
Updated Dec 02, 2024 · Source: OSV.dev | ||
1.1.0
minor
1 CVE
GHSA-4ph2-8337-hm62
Feb 08, 2021
Key Caching behavior in the DynamoDB Encryption Client.
Low
ImpactThis 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. PatchesFixed as of 1.3.0. We recommend users to modify their code and adopt WorkaroundsUsers who cannot upgrade to use the Affected versions
1.0.0
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.6
1.0.7
1.1.0
1.1.1
1.2.0
Fixed in
1.3.0
References
Updated Dec 02, 2024 · Source: OSV.dev | ||
1.0.7
patch
1 CVE
GHSA-4ph2-8337-hm62
Feb 08, 2021
Key Caching behavior in the DynamoDB Encryption Client.
Low
ImpactThis 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. PatchesFixed as of 1.3.0. We recommend users to modify their code and adopt WorkaroundsUsers who cannot upgrade to use the Affected versions
1.0.0
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.6
1.0.7
1.1.0
1.1.1
1.2.0
Fixed in
1.3.0
References
Updated Dec 02, 2024 · Source: OSV.dev | ||
1.0.6
patch
1 CVE
GHSA-4ph2-8337-hm62
Feb 08, 2021
Key Caching behavior in the DynamoDB Encryption Client.
Low
ImpactThis 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. PatchesFixed as of 1.3.0. We recommend users to modify their code and adopt WorkaroundsUsers who cannot upgrade to use the Affected versions
1.0.0
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.6
1.0.7
1.1.0
1.1.1
1.2.0
Fixed in
1.3.0
References
Updated Dec 02, 2024 · Source: OSV.dev | ||
1.0.5
patch
1 CVE
GHSA-4ph2-8337-hm62
Feb 08, 2021
Key Caching behavior in the DynamoDB Encryption Client.
Low
ImpactThis 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. PatchesFixed as of 1.3.0. We recommend users to modify their code and adopt WorkaroundsUsers who cannot upgrade to use the Affected versions
1.0.0
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.6
1.0.7
1.1.0
1.1.1
1.2.0
Fixed in
1.3.0
References
Updated Dec 02, 2024 · Source: OSV.dev | ||
1.0.4
patch
1 CVE
GHSA-4ph2-8337-hm62
Feb 08, 2021
Key Caching behavior in the DynamoDB Encryption Client.
Low
ImpactThis 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. PatchesFixed as of 1.3.0. We recommend users to modify their code and adopt WorkaroundsUsers who cannot upgrade to use the Affected versions
1.0.0
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.6
1.0.7
1.1.0
1.1.1
1.2.0
Fixed in
1.3.0
References
Updated Dec 02, 2024 · Source: OSV.dev | ||
1.0.3
patch
1 CVE
GHSA-4ph2-8337-hm62
Feb 08, 2021
Key Caching behavior in the DynamoDB Encryption Client.
Low
ImpactThis 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. PatchesFixed as of 1.3.0. We recommend users to modify their code and adopt WorkaroundsUsers who cannot upgrade to use the Affected versions
1.0.0
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.6
1.0.7
1.1.0
1.1.1
1.2.0
Fixed in
1.3.0
References
Updated Dec 02, 2024 · Source: OSV.dev | ||
1.0.2
patch
1 CVE
GHSA-4ph2-8337-hm62
Feb 08, 2021
Key Caching behavior in the DynamoDB Encryption Client.
Low
ImpactThis 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. PatchesFixed as of 1.3.0. We recommend users to modify their code and adopt WorkaroundsUsers who cannot upgrade to use the Affected versions
1.0.0
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.6
1.0.7
1.1.0
1.1.1
1.2.0
Fixed in
1.3.0
References
Updated Dec 02, 2024 · Source: OSV.dev | ||
1.0.1
patch
1 CVE
GHSA-4ph2-8337-hm62
Feb 08, 2021
Key Caching behavior in the DynamoDB Encryption Client.
Low
ImpactThis 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. PatchesFixed as of 1.3.0. We recommend users to modify their code and adopt WorkaroundsUsers who cannot upgrade to use the Affected versions
1.0.0
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.6
1.0.7
1.1.0
1.1.1
1.2.0
Fixed in
1.3.0
References
Updated Dec 02, 2024 · Source: OSV.dev | ||
1.0.0
initial
1 CVE
GHSA-4ph2-8337-hm62
Feb 08, 2021
Key Caching behavior in the DynamoDB Encryption Client.
Low
ImpactThis 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. PatchesFixed as of 1.3.0. We recommend users to modify their code and adopt WorkaroundsUsers who cannot upgrade to use the Affected versions
1.0.0
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.6
1.0.7
1.1.0
1.1.1
1.2.0
Fixed in
1.3.0
References
Updated Dec 02, 2024 · Source: OSV.dev |