Vulnerability DatabaseGHSA-w736-hf9p-qqh3

GHSA-w736-hf9p-qqh3
Java vulnerability analysis and mitigation

Overview

A low severity vulnerability (GHSA-w736-hf9p-qqh3) was identified in the DynamoDB Encryption Client's MostRecentProvider component, affecting versions prior to 1.15.0. The vulnerability was discovered and disclosed on February 4, 2021, impacting the aws-dynamodb-encryption-java package. The issue specifically affects implementations using MostRecentProvider in conjunction with key providers like AWS Key Management Service that support modifiable key permissions (GitHub Advisory).

Technical details

The vulnerability stems from a flaw in the time-based key reauthorization logic within MostRecentProvider. When key usage permissions were modified at the key provider level, the MostRecentProvider failed to properly reauthorize the key usage. This created a security gap where keys could potentially continue to be used in the DynamoDB Encryption Client even after their permissions had been revoked at the key provider level (GitHub Advisory, AWS Changelog).

Impact

The vulnerability could allow continued use of cryptographic keys in the DynamoDB Encryption Client after their permissions had been explicitly revoked at the key provider level. This could potentially lead to unauthorized access to encrypted data or bypass of intended access restrictions (GitHub Advisory).

Exploitability

The vulnerability requires specific conditions to be exploited, including the use of MostRecentProvider with a key provider that supports modifiable key permissions, such as AWS Key Management Service. The severity is rated as Low, suggesting limited real-world exploitability (GitHub Advisory).

Mitigation and workarounds

The vulnerability was patched in version 1.15.0 with the introduction of CachingMostRecentProvider, which replaces the deprecated MostRecentProvider. Users are strongly recommended to upgrade to version 1.15.0 or later and modify their code to use CachingMostRecentProvider. For users unable to upgrade immediately, a temporary workaround is available by calling clear() on the cache to manually flush its contents, which forces re-validation of the key with the key provider on next use (GitHub Advisory).

Additional resources


SourceThis report was generated using AI

Related Java vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-10050HIGH8.7
  • Java logoJava
  • jenkins
NoYesAug 04, 2026
CVE-2026-48048HIGH7.5
  • Java logoJava
  • org.xwiki.platform:xwiki-platform-livetable-ui
NoYesAug 10, 2026
CVE-2026-56818MEDIUM6.5
  • Java logoJava
  • netty-javadoc
NoYesAug 07, 2026
CVE-2026-48047MEDIUM5.9
  • Java logoJava
  • org.xwiki.platform:xwiki-platform-webjars-api
NoYesAug 07, 2026
CVE-2026-71497MEDIUM4.7
  • Java logoJava
  • javapackages-tools:201801::maven-wagon-http-lightweight
NoYesAug 06, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management