dbcve.org
LinkisApplication · Apache

CVE-2023-49566

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, due to the lack of effective filtering of parameters, an attacker configuring malicious db2 parameters in the DataSource Manager Module will result in jndi injection. Therefore, the parameters in the DB2 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.5.0 will be affected. We recommend users upgrade the version of 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 versions 1.5.0 and below contain a JNDI injection vulnerability in the DataSource Manager Module. Attackers with valid Linkis credentials can inject malicious JNDI references through unsanitized DB2 connection parameters in the database URL, potentially achieving remote code execution.

MitigationUpgrade Apache Linkis to version 1.6.0 which implements proper DB2 URL parameter blacklisting to block JNDI injection vectors.

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 installed Apache Linkis version
    Check the Linkis installation directory for a version file or check the pom.xml/build.gradle if source is available. Common locations: $LINKIS_HOME/conf/linkis.properties (linkis.version property) or check the WAR/JAR manifest.
    Affected if The installed version is 1.4.0 or any version >= 1.4.0 but less than 1.6.0
  2. Verify DataSource Manager Module is accessible
    Check if the DataSource Manager Module is enabled in the Linkis configuration at $LINKIS_HOME/conf/linkis.properties (wds.linkis.ms.datasource.enable=true) or through the management console.
    Affected if The DataSource Manager Module is enabled (value set to true)
  3. Identify configured DB2 datasources
    Review Linkis datasource configuration files or database for any registered datasources with type DB2. Query the linkis_datasource_type or linkis_datasource table in the Linkis metadata database.
    Affected if Any DB2-type datasources are registered in the Linkis datasource management system
  4. Inspect datasource connection URLs for JNDI patterns
    Examine the stored DB2 connection URLs in the datasource configuration. Look for parameters containing 'jndi', 'ldap', 'rmi', or 'java.naming' patterns in the URL or connection properties.
    Affected if DB2 connection URLs contain JNDI reference parameters (such as InitialContextFactory, ProviderURL, or JNDI naming references)
  5. Review logs for JNDI injection attempts
    Search Linkis gateway and datasource service logs (linkis-gateway.log, linkis-datasource*.log) for patterns like 'jndi:', 'ldap://', 'rmi://' in datasource-related request parameters.
    Affected if Historical or recent logs show JNDI injection attempts in datasource parameter fields

A user is affected if they run Apache Linkis version 1.4.0 through any version below 1.6.0 AND have the DataSource Manager Module enabled with DB2 datasources configured.

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 Apache Linkis to version 1.6.0 which implements proper DB2 URL parameter blacklisting to block JNDI injection vectors.

Recommended fix High confidence

1.6.0

  1. Obtain Apache Linkis version 1.6.0 from the official Apache repository (https://linkis.apache.org/)
  2. Backup the current Linkis installation, configuration, and database
  3. Stop the current Linkis services
  4. Deploy version 1.6.0 to replace the current installation
  5. Start the Linkis 1.6.0 services
  6. Verify the DataSource Manager Module functions correctly and the JNDI injection vulnerability is resolved
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
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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