dbcve.org
LinkisApplication · Apache

CVE-2023-46801

HIGH · 8.8 CVSS v3.1 Published 2024-07-15
Fix available
A fix is available. Upgrade to 1.6.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.5.0, data source management module, when adding Mysql data source, exists remote code execution vulnerability for java version < 1.8.0_241. The deserialization vulnerability exploited through jrmp can inject malicious files into the server and execute them. This attack requires the attacker to obtain an authorized account from Linkis before it can be carried out.  We recommend that users upgrade the java version to >= 1.8.0_241. Or users upgrade Linkis to version 1.6.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.5.0 contains a deserialization vulnerability in the data source management module when adding MySQL data sources. The flaw allows remote code execution through Java Remote Method Protocol (JRMP) by injecting malicious files for execution, but requires an attacker to first obtain an authorized Linkis account.

MitigationUpgrade Java to version >= 1.8.0_241 OR upgrade Apache Linkis to version 1.6.0 to remediate this vulnerability.

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.4.0, < 1.6.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 version
    Locate and inspect the Linkis version file or check the management console for the installed version number. Compare against the affected range: >= 1.4.0 and < 1.6.0.
    Affected if The installed version falls within 1.4.0 through 1.5.x (any version below 1.6.0).
  2. Confirm data source management module is accessible
    Verify that the data source management module is enabled and accessible in the Linkis deployment. This is typically found in the web UI under datasource management or via API endpoint.
    Affected if The data source management module is enabled and accessible to authenticated users.
  3. Check for MySQL data source configuration capability
    Determine if users have the ability to add or configure MySQL data sources through the data source management interface. This is the specific attack vector for CVE-2023-46801.
    Affected if Users with Linkis accounts can add MySQL data sources in the data source management module.
  4. Verify Linkis user authentication is in place
    Confirm that Linkis user accounts exist and authentication is required to access the data source management module.
    Affected if The vulnerability requires an authorized Linkis account, so if authentication is disabled or bypassed, the attack surface expands.

You are affected if Apache Linkis version is 1.4.0 through 1.5.x and the data source management module with MySQL data source configuration is accessible to authenticated users.

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.6.0 or later
Fixed in 1.6.0
Interim mitigation

Upgrade Java to version >= 1.8.0_241 OR upgrade Apache Linkis to version 1.6.0 to remediate this vulnerability.

Recommended fix High confidence

Apache Linkis 1.6.0

  1. 1. Back up your current Linkis configuration and data
  2. 2. Download Apache Linkis version 1.6.0 or later from the official Apache repository (https://linkis.apache.org/)
  3. 3. Stop the Linkis service
  4. 4. Upgrade Linkis to version 1.6.0 following the upgrade documentation
  5. 5. Restart the Linkis service
  6. 6. Verify the data source management module functions correctly
  7. 7. As an additional defense-in-depth measure, ensure Java version is >= 1.8.0_241
Caveat Review release notes for any configuration or API changes between your current version and 1.6.0

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

Fix this in Linkis Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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