dbcve.org
LinkisApplication · Apache

CVE-2023-27602

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, The PublicService module uploads files without restrictions on the path to the uploaded files, and file types. We recommend users upgrade the version of Linkis to version 1.3.2.  For versions <=1.3.1, we suggest turning on the file path check switch in linkis.properties `wds.linkis.workspace.filesystem.owner.check=true` `wds.linkis.workspace.filesystem.path.check=true`

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 PublicService module allows unrestricted file uploads without validating file paths (enabling path traversal) or file types. An unauthenticated attacker could upload malicious files to arbitrary locations on the server, potentially achieving remote code execution.

MitigationUpgrade to Linkis 1.3.2 or alternatively enable the workspace filesystem security checks by setting wds.linkis.workspace.filesystem.owner.check=true and wds.linkis.workspace.filesystem.path.check=true in linkis.properties.

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 Linkis installation directory and check the version file or pom.xml. Common paths include /opt/linkis/, /usr/local/linkis/, or check the JAR file version in the lib directory.
    Affected if The installed version is 1.3.1 or lower.
  2. Verify workspace filesystem security configuration
    Inspect the linkis.properties configuration file (typically in $LINKIS_HOME/conf/) for the properties wds.linkis.workspace.filesystem.owner.check and wds.linkis.workspace.filesystem.path.check. Check if they are set to true.
    Affected if These security properties are absent or set to false/false, leaving path traversal checks disabled.
  3. Confirm PublicService module exposure
    Identify if the PublicService REST APIs are network-accessible. Check server configuration files (like linkis.properties or deployment configs) for the publicservice.host and port settings, and verify network accessibility.
    Affected if The PublicService endpoint is externally accessible without authentication.
  4. Check file upload endpoint accessibility
    Review the deployed application's API endpoints or proxy configuration to determine if the file upload functionality (typically under /filesystem/ directory) is reachable.
    Affected if File upload endpoints are reachable without authentication and security checks are disabled.

A user is affected if Apache Linkis version is 1.3.1 or lower AND the workspace filesystem security properties (owner.check and path.check) are not enabled to true.

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 to Linkis 1.3.2 or alternatively enable the workspace filesystem security checks by setting wds.linkis.workspace.filesystem.owner.check=true and wds.linkis.workspace.filesystem.path.check=true in linkis.properties.

Recommended fix High confidence

1.3.2

  1. Upgrade Apache Linkis to version 1.3.2 or later as the primary remediation
  2. If immediate upgrade is not feasible, edit the linkis.properties configuration file
  3. Add or modify the following properties in linkis.properties: wds.linkis.workspace.filesystem.owner.check=true
  4. Add or modify: wds.linkis.workspace.filesystem.path.check=true
  5. Restart all Linkis services (PublicService and related modules) to apply configuration changes
  6. Verify file upload functionality works correctly after changes

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

Fix this in Linkis Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
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,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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