CVE-2024-26579: Apache Inlong JDBC Vulnerability
Deserialization of Untrusted Data vulnerability in Apache InLong. This issue affects Apache InLong: from 1.7.0 through 1.11.0. The attackers can bypass using malicious parameters.
Users are advised to upgrade to Apache InLong's 1.12.0 or cherry-pick [1], [2] to solve it.
[1] https://github.com/apache/inlong/pull/9694
[2] https://github.com/apache/inlong/pull/9707
Other sources
Deserialization of Untrusted Data vulnerability in Apache InLong.This issue affects Apache InLong: from 1.7.0 through 1.11.0,
the attackers can bypass using malicious parameters.
Users are advised to upgrade to Apache InLong's 1.12.0 or cherry-pick [1], [2] to solve it.
[1] https://github.com/apache/inlong/pull/9694
[2] https://github.com/apache/inlong/pull/9707
— NVD
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-26579?
CVE-2024-26579 is classified as a high severity vulnerability due to its potential for exploitation through deserialization of untrusted data.
How do I fix CVE-2024-26579?
To fix CVE-2024-26579, upgrade to Apache InLong version 1.12.0 or cherry-pick specific commits that address the vulnerability.
What versions of Apache InLong are affected by CVE-2024-26579?
Apache InLong versions from 1.7.0 to 1.11.0 are affected by CVE-2024-26579.
What type of vulnerability is CVE-2024-26579?
CVE-2024-26579 is a deserialization of untrusted data vulnerability.
Who is impacted by CVE-2024-26579?
Any user or organization utilizing Apache InLong versions 1.7.0 to 1.11.0 is impacted by CVE-2024-26579.