dbcve.org
LinkisApplication · Apache

CVE-2022-39944

HIGH · 8.8 CVSS v3.1 Published 2022-10-26
Fix available
A fix is available. Upgrade to after 1.2.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
In Apache Linkis <=1.2.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 a JDBC EC with a MySQL data source and malicious parameters. Therefore, the parameters in the jdbc url should be blacklisted. Versions of Apache Linkis <= 1.2.0 will be affected, We recommend users to update to 1.3.0.

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 confidence

Apache Linkis <=1.2.0 contains a deserialization vulnerability when using MySQL Connector/J, where an attacker with database write access who can configure a JDBC Engine Connector with a MySQL data source can inject malicious parameters into the JDBC URL to achieve remote code execution.

MitigationUpdate to Apache Linkis 1.3.0 or later, and implement JDBC URL parameter blacklisting as a defense-in-depth measure.

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
Affected:<= 1.2.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Linkis installation and version
    Locate the Linkis installation directory and check the version file or pom.xml. Common locations include /opt/linkis or the installation root. Look for a version file or examine the pom.xml in the lib directory.
    Affected if The installed version is 1.2.0 or any version lower than 1.2.0
  2. Verify MySQL Connector/J is in use
    Check the lib or libs directory for mysql-connector-java.jar or any MySQL JDBC driver JAR files. Also check the classpath configuration files for MySQL driver references.
    Affected if MySQL Connector/J driver is present in the Linkis installation
  3. Examine JDBC Engine Connector configuration for MySQL data sources
    Look for datasource configuration files (typically in conf/ or similar directories) that define JDBC connections. Search for files containing 'jdbc:mysql' URLs or MySQL datasource configurations under the JDBC Engine Connector settings.
    Affected if A JDBC Engine Connector is configured to connect to a MySQL database using a JDBC URL
  4. Review database access controls for connector configuration
    Identify which users or entities have write access to the database that stores connector configurations. Check if untrusted users can modify JDBC connection parameters in the datasource settings.
    Affected if Users with only database write access (without Linkis admin privileges) can configure or modify JDBC Engine Connector settings with arbitrary JDBC URL parameters
  5. Inspect JDBC URL parameters in MySQL datasource configurations
    Review the actual JDBC connection URL strings in the datasource configuration files. Look for any suspicious or unexpected parameters appended to the URL, particularly parameters related to classes that may trigger deserialization.
    Affected if The JDBC URL contains parameters that could enable deserialization attacks (such as parameters loading external Java classes)

You are affected if running Apache Linkis version 1.2.0 or lower with a JDBC Engine Connector configured to use MySQL, where an attacker can inject arbitrary parameters into the JDBC connection URL.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.2.0
Interim mitigation

Update to Apache Linkis 1.3.0 or later, and implement JDBC URL parameter blacklisting as a defense-in-depth measure.

Recommended fix High confidence

1.3.0

  1. Stop the Linkis service to prevent any active connections during upgrade
  2. Create a complete backup of the current Linkis installation directory and associated database
  3. Download Apache Linkis version 1.3.0 from the official Apache download repository
  4. Upgrade Linkis to version 1.3.0 by following the official upgrade documentation
  5. After upgrading, ensure the MySQL JDBC connection configurations are properly reviewed and secured
  6. Restart the Linkis service
  7. Verify that the Linkis components are running correctly and the MySQL data source connections are functional
Caveat Review the 1.3.0 release notes for any breaking changes between 1.2.0 and 1.3.0

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linkis Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-39944 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-39944 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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