dbcve.org
LinkisApplication · Apache

CVE-2023-27603

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, due to the Manager module engineConn material upload does not check the zip path, This is a Zip Slip issue, which will lead to a potential RCE vulnerability. 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 <=1.3.1 contains a Zip Slip vulnerability in the Manager module's engineConn material upload feature, where uploaded zip files are extracted without validating extraction paths, allowing directory traversal that can overwrite system files and achieve remote code execution.

MitigationUpgrade Apache Linkis to version 1.3.2 or later to address the path traversal vulnerability in zip extraction.

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 version
    Locate the installed Linkis binaries or check the version file (typically in the installation directory under conf or the deployed web application's manifest). Run: ls -la [linkis-home]/lib/*linkis*.jar or check version.info files.
    Affected if The installed version is 1.3.1 or lower.
  2. Verify Manager module is deployed
    Check if the Manager service is running and accessible. Look for the Manager module's REST API endpoints (typically under /api/rest_J_1_1/linkis-manager/ or similar paths). Check process list: ps aux | grep linkis-manager.
    Affected if The Manager module is deployed and running.
  3. Check engineConn material upload endpoint exposure
    Identify if the engineConn upload API is accessible. Look for endpoints related to material/upload or engineConn/upload in the Linkis Manager module. Check configuration files (linkis-manager.properties) for upload-related settings and the exposed REST API paths.
    Affected if The upload endpoint is exposed via HTTP/HTTPS without additional authentication beyond Linkis login.
  4. Review upload extraction logic
    Examine the deployed Manager module JAR files for the extraction code. Search for ZipInputStream or unzip patterns in the compiled code or source if available. The vulnerable code would be in the material management upload handling.
    Affected if The code lacks path validation (check for getNextEntry() followed by file creation without path traversal safeguards).

You are affected if Apache Linkis version is 1.3.1 or lower AND the Manager module's engineConn material upload feature is accessible to potential attackers.

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 address the path traversal vulnerability in zip extraction.

Recommended fix High confidence

1.3.2

  1. 1. Back up your current Apache Linkis installation and all related data
  2. 2. Download Apache Linkis version 1.3.2 from the official Apache downloads page (https://linkis.apache.org/download)
  3. 3. Stop the running Linkis services
  4. 4. Install or deploy Linkis 1.3.2 following the standard deployment documentation
  5. 5. Restart the Linkis services
  6. 6. Verify the upgrade by checking that the Manager module properly handles engineConn material uploads and that path traversal is prevented

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
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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