How severe is GHSA-w736-hf9p-qqh3?

No CVSS score has been assigned to GHSA-w736-hf9p-qqh3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w736-hf9p-qqh3?

GHSA-w736-hf9p-qqh3 affects the following packages: com.amazonaws:aws-dynamodb-encryption-java (Maven). Ecosystems affected: Maven.

How do I fix GHSA-w736-hf9p-qqh3?

Update com.amazonaws:aws-dynamodb-encryption-java to 1.15.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w736-hf9p-qqh3 is resolved across your whole dependency graph.

How do I detect GHSA-w736-hf9p-qqh3 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.amazonaws:aws-dynamodb-encryption-java, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-w736-hf9p-qqh3 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-w736-hf9p-qqh3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-w736-hf9p-qqh3 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-w736-hf9p-qqh3 published, and has it been updated?

GHSA-w736-hf9p-qqh3 was published on February 8, 2021 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

Key Caching behavior in the DynamoDB Encryption ClientGHSA-w736-hf9p-qqh3

Fix: aws/aws-dynamodb-encryption-java@7de5f5a

GHSA-w736-hf9p-qqh3 is a security vulnerability in com.amazonaws:aws-dynamodb-encryption-java. A fix is available for com.amazonaws:aws-dynamodb-encryption-java — see the affected versions and patch details below.

Published

Feb 8, 2021

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕com.amazonaws:aws-dynamodb-encryption-java

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.amazonaws:aws-dynamodb-encryption-java`	all versions	1.15.0`com.amazonaws:aws-dynamodb-encryption-java:1.15.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.amazonaws:aws-dynamodb-encryption-java, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.amazonaws:aws-dynamodb-encryption-java to 1.15.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w736-hf9p-qqh3 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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 `CachingMostR

O3 Security · Impact-Aware SCA

Is GHSA-w736-hf9p-qqh3 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works