dbcve.org
LinkisApplication · Apache

CVE-2024-27181

HIGH · 8.8 CVSS v3.1 Published 2024-08-02
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, Privilege Escalation in Basic management services where the attacking user is a trusted account allows access to Linkis's Token information. Users are advised to upgrade to version 1.6.0, which fixes this issue.

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 · moderate confidence

Apache Linkis versions 1.5.0 and earlier contain a privilege escalation vulnerability in the Basic management services component. An attacker with a trusted account can escalate privileges to gain unauthorized access to Linkis's Token information, which could lead to further authentication bypass or data exposure.

MitigationUpgrade to Apache Linkis version 1.6.0 or later. Before upgrading, inventory all trusted accounts and review token access controls as part of the migration.

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.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 installed version
    Check the Linkis installation directory for version information. Common locations: check VERSION file in installation root, or query the Linkis management console for the version metadata. Run: ls -la <linkis_install_dir>/VERSION or look in the About section of the Linkis web console.
    Affected if Installed version is 1.5.0 or earlier (any version < 1.6.0)
  2. Confirm Token management module is enabled
    Verify that the Token management service/endpoint is enabled in Linkis configuration. Check configuration files (linkis.properties or similar) for token-related settings such as wds.linkis.token.enable or token.service.enabled. Also verify the token management REST API endpoints are accessible.
    Affected if Token management module is active and accessible via REST API or web interface
  3. Review token management endpoint access controls
    Examine the access control configuration for token management endpoints. Check if the endpoints allow authenticated users with lower privileges to access token information. Look for any configuration that controls who can call /api/linkisManager/token/* or similar token management routes.
    Affected if Token endpoints do not enforce proper privilege escalation checks, allowing lower-privilege authenticated users to retrieve token credentials
  4. Audit existing trusted accounts
    List all accounts marked as 'trusted' in the Linkis user database or configuration. Query the underlying database for users with trust relationship flags or check linkis-mg.properties for trusted.user.list settings.
    Affected if Multiple trusted accounts exist, particularly any with reduced privilege levels compared to admin accounts

You are affected if your Apache Linkis installation is version 1.5.0 or earlier, the token management module is enabled, and lower-privilege trusted users can access token credential endpoints without proper authorization checks.

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 to Apache Linkis version 1.6.0 or later. Before upgrading, inventory all trusted accounts and review token access controls as part of the migration.

Recommended fix High confidence

Apache Linkis 1.6.0

  1. 1. Back up the current Apache Linkis installation, including configuration files and databases
  2. 2. Stop the Linkis service to prevent any active connections during upgrade
  3. 3. Download Apache Linkis version 1.6.0 from the official Apache distribution mirrors (https://dl.apache.org/linkis/)
  4. 4. Install version 1.6.0 following the standard upgrade documentation for your deployment method (manual, Docker, Kubernetes, etc.)
  5. 5. Restore any custom configurations from the backup, ensuring compatibility with version 1.6.0
  6. 6. Start the Linkis service and verify it runs without errors
  7. 7. Validate that the privilege escalation vulnerability is resolved by testing token access with non-admin trusted accounts
Caveat Review release notes for 1.6.0 for any configuration or API changes that may affect existing workflows

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

Fix this in Linkis Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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