dbcve.org
LinkisApplication · Apache

CVE-2024-45627

MEDIUM · 5.9 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 1.7.0 or later.
See remediation →
64/100
Remediation priority · Elevated
No privileges 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.7.0, due to the lack of effective filtering of parameters, an attacker configuring malicious Mysql JDBC parameters in the DataSource Manager Module will allow the attacker to read arbitrary files from the Linkis server. Therefore, the parameters in the Mysql JDBC URL should be blacklisted. This attack requires the attacker to obtain an authorized account from Linkis before it can be carried out. Versions of Apache Linkis < 1.7.0 will be affected. We recommend users upgrade the version of Linkis to version 1.7.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

In Apache Linkis < 1.7.0, the DataSource Manager Module lacks proper parameter filtering for MySQL JDBC connections, allowing authenticated attackers to inject malicious JDBC parameters that enable arbitrary file read from the server filesystem.

MitigationUpgrade Apache Linkis to version 1.7.0 which implements a blacklist for dangerous MySQL JDBC URL parameters.

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.7.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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Determine Apache Linkis installed version
    Locate the Linkis installation directory and check the version file or pom.xml, or run 'linkis --version' if available
    Affected if Version is below 1.7.0 (e.g., 1.6.0, 1.5.0, etc.)
  2. Verify DataSource Manager Module is enabled
    Check the Linkis configuration files (typically in conf/ or config/) for the datasource-related module settings, or inspect the deployed microservices for the datasource-manager service
    Affected if DataSource Manager Module is deployed and accessible in the environment
  3. Confirm MySQL JDBC data source capability exists
    Review the DataSource Manager configurations or database connection settings to confirm MySQL data sources can be created or accessed
    Affected if MySQL JDBC connections can be configured through the DataSource Manager Module
  4. Verify user authentication to DataSource Manager is possible
    Check if users can authenticate to the DataSource Manager Module (typically via Linkis general authentication mechanisms like username/password or token)
    Affected if Authenticated users or attackers can access the DataSource Manager Module to configure JDBC connections

The environment is affected if Apache Linkis version is below 1.7.0 AND the DataSource Manager Module is enabled and accessible to authenticated users who can configure MySQL JDBC connections.

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 1.7.0 or later
Fixed in 1.7.0
Interim mitigation

Upgrade Apache Linkis to version 1.7.0 which implements a blacklist for dangerous MySQL JDBC URL parameters.

Recommended fix High confidence

1.7.0

  1. Back up the current Linkis installation and configuration
  2. Download Apache Linkis version 1.7.0 from the official Apache repository
  3. Stop the Linkis service
  4. Install version 1.7.0 following the standard upgrade documentation
  5. Start the Linkis service
  6. Verify the DataSource Manager Module is functioning correctly
  7. Confirm the vulnerability is patched by testing that arbitrary file read via JDBC parameters is no longer possible

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

Fix this in Linkis Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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