Apache Linkis (incubating): The DatasourceManager module has a serialization attack vulnerability
Description
In Apache Linkis <=1.3.0 when used with the MySQL Connector/J, a deserialization vulnerability with possible remote code execution impact exists when an attacker has write access to a database and configures new datasource with a MySQL data source and malicious parameters. Therefore, the parameters in the jdbc url should be blacklisted. Versions of Apache Linkis <= 1.3.0 will be affected.
We recommend users to upgrade the version of Linkis to version 1.3.1.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A deserialization vulnerability in Apache Linkis <=1.3.0, when used with MySQL Connector/J, allows remote code execution if an attacker has write access to a database.
Vulnerability
Description
CVE-2022-44645 is a deserialization vulnerability in Apache Linkis versions <= 1.3.0 that manifests when the system is used with the MySQL Connector/J library. The root cause is that Linkis does not properly sanitize parameters in JDBC URLs when configuring a MySQL data source. An attacker with write access to a database can craft a malicious JDBC URL containing serialized objects that, upon deserialization by the MySQL Connector/J, can lead to arbitrary code execution [1][2].
Exploitation
Prerequisites and Attack Surface
Exploitation requires the attacker to have write access to a database that Linkis can connect to, and the ability to configure a new datasource within Linkis using a MySQL data source. The attacker then injects malicious parameters into the JDBC URL, exploiting the deserialization flaw. There is no mention of authentication being required beyond the database write access, but the attacker must be able to interact with Linkis to create or modify datasource configurations [2].
Impact
Successful exploitation results in remote code execution on the server running Linkis, under the privileges of the Linkis process. This could lead to full compromise of the Linkis instance and potentially lateral movement within the network, as the attacker could execute arbitrary commands, access sensitive data, or further pivot to other systems [1][2].
Mitigation
Users are strongly advised to upgrade to Apache Linkis version 1.3.1, which includes a blacklist of dangerous JDBC URL parameters to prevent deserialization attacks. No workaround is provided for earlier versions beyond upgrading, and this vulnerability is not listed in CISA's Known Exploited Vulnerabilities catalog as of the analysis date [2].
AI Insight generated on May 20, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
org.apache.linkis:linkisMaven | < 1.3.1 | 1.3.1 |
Affected products
2- Apache Software Foundation/Apache Linkis (incubating)v5Range: 0
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
3- github.com/advisories/GHSA-h6w8-52mq-4qxcghsaADVISORY
- lists.apache.org/thread/zlcfmvt65blqc4n6fxypg6f0ns8fqfz4ghsavendor-advisoryWEB
- nvd.nist.gov/vuln/detail/CVE-2022-44645ghsaADVISORY
News mentions
0No linked articles in our index yet.