GHSA-wmmv-vvg5-993q — redshift-jdbc42
HIGHGHSA-wmmv-vvg5-993q is a high-severity (CVSS 8.1) CWE-470 vulnerability in com.amazon.redshift:redshift-jdbc42. A fix is available for com.amazon.redshift:redshift-jdbc42 — see the affected versions and patch details below.
Amazon Redshift Vulnerable to Remote Code Execution via Unsafe Class Loading
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-wmmv-vvg5-993q.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-wmmv-vvg5-993q by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 380,066 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
com.amazon.redshift:redshift-jdbc42Real-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
Summary
Amazon Redshift JDBC Driver is a Type 4 JDBC driver that provides database connectivity through the standard JDBC application program interfaces (APIs). An issue exists in versions prior to 2.2.2 where the driver could load arbitrary classes when processing certain connection URL parameters, potentially allowing code execution in the application context.
Impact
When a JDBC connection URL contains certain parameters, the driver processes the parameter values in a way that could trigger the execution of code from classes available on the application's classpath. An actor who can influence the JDBC connection URL could leverage this to execute code in the context of the application's JVM process. Successful exploitation could allow the actor to read sensitive data, modify application state, or disrupt service availability with the privileges of the application process.
Impacted versions: Amazon Redshift JDBC Driver < 2.2.2
Patches
This issue has been addressed in Amazon Redshift JDBC Driver version 2.2.2. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
References
If you have any questions or comments about this advisory, we ask that you contact AWS Security via our vulnerability reporting page or directly via email to [email protected]. Please do not create a public GitHub issue.
Acknowledgement
We would like to thank Fushuling for collaborating on this issue through the coordinated issue disclosure process.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.amazon.redshift:redshift-jdbc42 | all versions | 2.2.2com.amazon.redshift:redshift-jdbc42:2.2.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.amazon.redshift:redshift-jdbc42, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.amazon.redshift:redshift-jdbc42 to 2.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wmmv-vvg5-993q 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
Is GHSA-wmmv-vvg5-993q in your dependencies?
Find it across Maven, including transitive dependencies.