CVE-2022-40955 Deserialization attack in Apache InLong prior to version 1.3.0 allows RCE via JDBC

High 8.8 Published Updated

An attacker with database write access can trigger remote code execution on Apache InLong servers via unsafe JDBC deserialization.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2022-40955?

CVE-2022-40955 is a high-severity unsafe deserialization vulnerability in Apache InLong, published on 20 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

In versions of Apache InLong prior to 1.3.0, an attacker with sufficient privileges to specify MySQL JDBC connection URL parameters and to write arbitrary data to the MySQL database, could cause this data to be deserialized by Apache InLong, potentially leading to Remote Code Execution on the Apache InLong server. Users are advised to upgrade to Apache InLong 1.3.0 or newer.

Weakness: CWE-502

Which versions are affected by CVE-2022-40955?

2 open source packages ship an affected version, including org.apache.inlong:inlong-common. It affects 1 product.

PackageAffectedFixed in
org.apache.inlong:inlong-common MavenAll versions1.3.0
org.apache.inlong:inlong-common MavenAll versions1.3.0

Products include Apache Inlong.

How do I fix CVE-2022-40955?

Upgrade org.apache.inlong:inlong-common to 1.3.0 or later.

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

Is CVE-2022-40955 being exploited?

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

Sources

Also known as GHSA-26m4-qjp9-xmc6.

Is CVE-2022-40955 in your software?

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

Check your SBOMs for free