LinkisApplication · Apache
CVE-2022-44645
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache Linkis <=1.3.0 contains a deserialization vulnerability exploitable through MySQL Connector/J when an attacker with database write access configures a MySQL datasource with malicious JDBC URL parameters, potentially achieving remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
LinkisApplication
<= 1.3.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Linkis versionLocate the installed Linkis binaries or libraries and determine the version number. Common locations include /opt/linkis, /usr/local/linkis, or the application's lib directory. Check for files named linkis-*.jar or version.properties.Affected if The installed version is 1.3.0 or lower (any version <= 1.3.0).
-
Confirm MySQL datasource functionality is in useSearch for MySQL connector configuration files, datasource definition files, or database connection settings within the Linkis configuration directories. Look for files containing 'mysql', 'datasource', or 'jdbc' keywords.Affected if MySQL datasources are configured and the Linkis version is <= 1.3.0.
-
Inspect MySQL datasource JDBC URL parametersExamine all MySQL datasource configuration files and identify the JDBC connection URL parameters. Look for entries in datasource configuration files that define connection strings (jdbc:mysql://...).Affected if Any JDBC URL contains suspicious parameters such as allowLoadLocalInfile, autoDeserialize, allowUrlInLocalInfile, or other potentially dangerous MySQL Connector/J parameters, combined with a Linkis version <= 1.3.0.
-
Review datasource configuration write accessDetermine which users or roles have permission to create or modify datasource configurations within Linkis. Check datasource management settings, access control lists, or user permissions files.Affected if Users other than administrators have write access to datasource configurations and the Linkis version is <= 1.3.0.
A user is affected if they are running Apache Linkis version 1.3.0 or lower with MySQL datasource functionality enabled and configured, particularly if non-admin users can modify datasource JDBC URL parameters.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to Apache Linkis 1.3.1 or later, which implements blacklist filtering for dangerous JDBC URL parameters.
1.3.1
- Backup your current Linkis installation and database
- Stop the Linkis service
- Download Apache Linkis version 1.3.1 from the official Apache repository
- Upgrade Linkis to version 1.3.1 following the standard upgrade documentation
- Restart the Linkis service
- Verify the upgrade was successful and the service is functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Linkis
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44645 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-44645 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data