dbcve.org
LinkisApplication · Apache

CVE-2022-44644

MEDIUM · 6.5 CVSS v3.1 Published 2023-01-31
Fix available
A fix is available. Upgrade to after 1.3.0 or later.
See remediation →
71/100
Remediation priority · Elevated
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.3.0 when used with the MySQL Connector/J in the data source module, an authenticated attacker could read arbitrary local files by connecting a rogue MySQL server, By adding allowLoadLocalInfile to true in the JDBC parameter. Therefore, the parameters in the JDBC URL should be blacklisted. Versions of Apache Linkis <= 1.3.0 will be affected.  We recommend users 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 confidence

In Apache Linkis <=1.3.0, the MySQL Connector/J in the data source module allows authenticated attackers to read arbitrary local files by configuring a rogue MySQL server and setting the allowLoadLocalInfile JDBC parameter to true, enabling local file inclusion via the JDBC driver.

MitigationUpgrade Apache Linkis to version 1.3.1 or later, and implement blacklist filtering for dangerous JDBC URL parameters such as allowLoadLocalInfile.

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.3.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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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. Check Apache Linkis installed version
    Run 'linkis --version' or check the version file in the Linkis installation directory. Compare against the affected version range of <= 1.3.0.
    Affected if The installed version is 1.3.0 or earlier.
  2. Determine if data source module is in use
    Inspect the Linkis configuration files (such as application-linkis.yml or equivalent) to see if the data source management module is enabled or configured.
    Affected if The data source module is enabled and configured to use MySQL connections.
  3. Inspect JDBC connection configurations
    Search through Linkis configuration files and any custom data source definitions for the parameter 'allowLoadLocalInfile' and verify its value.
    Affected if allowLoadLocalInfile is set to 'true' in any JDBC URL configuration.
  4. Review datasource connection settings
    Examine any data source connection configuration files or database connection definitions for MySQL Connector/J settings that enable local file loading.
    Affected if MySQL datasource configurations allow loading local files or have enabled the loadLocalInfile feature.

A user is affected if they are running Apache Linkis version 1.3.0 or earlier with the data source module enabled and MySQL connections configured with allowLoadLocalInfile=true.

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.3.0
Interim mitigation

Upgrade Apache Linkis to version 1.3.1 or later, and implement blacklist filtering for dangerous JDBC URL parameters such as allowLoadLocalInfile.

Recommended fix High confidence

1.3.1

  1. Upgrade Apache Linkis from version 1.3.0 or earlier to version 1.3.1
  2. After upgrading, verify that MySQL data source connections work correctly with the updated version
  3. Review and test any custom JDBC connection configurations in the data source module to ensure proper functionality

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

Fix this in Linkis Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-44644 — 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-44644 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