# CVE-2022-41828: com.amazon.redshift:redshift-jdbc42 vulnerable to remote command execution

> An attacker can execute arbitrary code by exploiting unsafe object instantiation in the Redshift JDBC driver.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Sep 2022
- **Updated:** 20 May 2025
- **Also known as:** GHSA-jc69-hjw2-fm86

## What is CVE-2022-41828?

CVE-2022-41828 is a high-severity unsafe deserialization vulnerability in n/a, published on 29 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

In Amazon AWS Redshift JDBC Driver (aka amazon-redshift-jdbc-driver or redshift-jdbc42) before 2.1.0.8, the Object Factory does not check the class type when instantiating an object from a class name.

Weakness: CWE-704 (Incorrect Type Conversion or Cast)

## Which versions are affected by CVE-2022-41828?

2 open source packages ship an affected version, including com.amazon.redshift:redshift-jdbc42. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.amazon.redshift:redshift-jdbc42` | Maven | All versions | 2.1.0.8 |
| `com.amazon.redshift:redshift-jdbc42` | Maven | All versions | 2.1.0.8 |

Products: Amazon Amazon Web Services Redshift Java Database Connectivity Driver.

## How do I fix CVE-2022-41828?

Upgrade com.amazon.redshift:redshift-jdbc42 to 2.1.0.8 or later.

## Is CVE-2022-41828 being exploited?

There is no known exploitation of CVE-2022-41828 in the wild and no public exploit code.

Public exploit code:

- [CVE-2022-41828] Amazon AWS Redshift JDBC Driver Remote Code Execution (RCE) (github_poc): https://github.com/murataydemir/CVE-2022-41828

## Other vulnerabilities in n/a

- [CVE-2024-12744](https://insights.sbomify.com/CVE-2024-12744/): SQL Injection in the Amazon Redshift JDBC Driver affecting v2.1.0.31 (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41828 and fix it if it is affected.

What it is: CVE-2022-41828 is a high-severity unsafe deserialization vulnerability in n/a, published on 29 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-41828 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.amazon.redshift:redshift-jdbc42 (Maven): affected all versions; fixed in 2.1.0.8
- com.amazon.redshift:redshift-jdbc42 (Maven): affected all versions; fixed in 2.1.0.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-41828/ (Markdown: https://insights.sbomify.com/CVE-2022-41828/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41828
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41828
- OSV: https://osv.dev/vulnerability/CVE-2022-41828

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-41828/
Summaries are generated and may contain mistakes; the official description above is the record.