dbcve.org
LinkisApplication · Apache

CVE-2023-29216

CRITICAL · 9.8 CVSS v3.1 Published 2023-04-10
Fix available
A fix is available. Upgrade to after 1.3.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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.3.1, because the parameters are not effectively filtered, the attacker uses the MySQL data source and malicious parameters to configure a new data source to trigger a deserialization vulnerability, eventually leading to remote code execution. Versions of Apache Linkis <= 1.3.0 will be affected. We recommend users upgrade the version of Linkis to version 1.3.2.

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 versions 1.3.0 and below have a deserialization vulnerability in the MySQL data source configuration. Because parameters are not effectively filtered, an attacker can configure a new data source with malicious parameters to trigger unsafe deserialization, leading to remote code execution.

MitigationUpgrade Apache Linkis to version 1.3.2 or later to remediate the parameter filtering issue that enables the deserialization attack.

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.1

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 installed version
    Locate the Linkis installation directory and check the version file or WAR/package manifest. Common locations include the release notes, version.properties, or the management console about page.
    Affected if The installed version is 1.3.1 or lower (any version <= 1.3.1)
  2. Determine if MySQL data source feature is in use
    Access the Linkis management console or configuration UI. Navigate to the data source management section and review any configured data sources, specifically checking for MySQL-type connections.
    Affected if A MySQL data source is configured or was previously configured in the system
  3. Inspect MySQL data source parameter configurations
    In the data source management interface, examine the connection parameters for any MySQL data sources. Look at the configuration properties stored for database connections.
    Affected if The data source parameters can be modified or include serialized objects without validation
  4. Check for unauthorized or suspicious data source entries
    Review all data source configurations in the database or configuration storage for unexpected entries, particularly those with unusual parameter patterns or serialized content.
    Affected if There are data sources with parameters that contain serialized objects or unexpected code
  5. Verify recent data source configuration changes
    Review audit logs, configuration change history, or database records tracking data source modifications for any recent changes to MySQL data source configurations.
    Affected if New data sources were created or modified, especially by unexpected users

You are affected if your Apache Linkis version is 1.3.1 or below AND you have MySQL data sources configured, since the vulnerability allows unsafe deserialization through data source parameters.

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

Upgrade Apache Linkis to version 1.3.2 or later to remediate the parameter filtering issue that enables the deserialization attack.

Recommended fix High confidence

1.3.2

  1. 1. Back up the current Linkis installation directory and database before starting the upgrade process
  2. 2. Stop the running Apache Linkis service to prevent data corruption during upgrade
  3. 3. Download Apache Linkis version 1.3.2 from the official Apache download mirrors (https://dl.apache.org/linkis/)
  4. 4. Extract the downloaded Linkis 1.3.2 archive to replace the existing installation
  5. 5. Review and migrate any custom configurations from the old installation to the new version (check conf/ directory)
  6. 6. Start the Apache Linkis 1.3.2 service
  7. 7. Verify the service is running correctly and test that data source functionality works as expected

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

Fix this in Linkis Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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