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

High 8.8 Published Updated

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

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

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

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.

PackageAffectedFixed in
com.amazon.redshift:redshift-jdbc42 MavenAll versions2.1.0.8
com.amazon.redshift:redshift-jdbc42 MavenAll versions2.1.0.8

Products include 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.

Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.

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: 1 proofs of concept on GitHub.

Sources

Also known as GHSA-jc69-hjw2-fm86.

Is CVE-2022-41828 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free