LinkisApplication · Apache

CVE-2024-39928

HIGH · 7.5 CVSS v3.1 Published 2024-09-25
Fix available
A fix is available. Upgrade to 1.6.0 or later.
See remediation →
84/100
Remediation priority · High
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.5.0, a Random string security vulnerability in Spark EngineConn, random string generated by the Token when starting Py4j uses the Commons Lang's RandomStringUtils. Users are recommended 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 below use the Commons Lang RandomStringUtils class to generate random tokens for Py4j authentication during Spark EngineConn startup. RandomStringUtils produces cryptographically weak, predictable random strings that could allow remote attackers to guess or brute-force tokens and potentially execute code via the Py4j gateway.

MitigationUpgrade to Apache Linkis 1.6.0 which replaces the insecure RandomStringUtils with a cryptographically secure random string generation mechanism.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Check Apache Linkis installed version
    Run 'linkis-version' or check the version file in the Linkis installation directory (usually in lib/linkis-files/ or the RELEASE file)
    Affected if The installed version is >= 1.3.0 and < 1.6.0
  2. Verify Py4j is enabled for Spark EngineConn
    Inspect the Linkis configuration file (linkis-cg-spark-core或者linkis-cg-engineplugin-config) or check for py4j configuration in the deploy/conf/ configuration directory
    Affected if Py4j authentication is enabled for Spark EngineConn (this is the vulnerable configuration path)
  3. Inspect Spark EngineConn logs for token generation
    Examine the EngineConn logs in the logs/ directory (typically linkis-cg-engineplugin/spark/engineConnLogs/) for messages related to Py4j gateway startup and token generation
    Affected if Logs show RandomStringUtils being used or mention Py4j tokens generated during startup (indicates the vulnerable code path is being executed)

A user is affected if their installed Apache Linkis version is between 1.3.0 and 1.5.x inclusive AND Py4j authentication is enabled for Spark EngineConn, which causes predictable random tokens to be generated during Spark job submission.

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 1.6.0 which replaces the insecure RandomStringUtils with a cryptographically secure random string generation mechanism.

Recommended fix High confidence

1.6.0

  1. Download Apache Linkis version 1.6.0 from the official Apache distribution (downloads.apache.org)
  2. Review the official upgrade documentation for your current version to 1.6.0
  3. Execute the upgrade following the documented migration steps
  4. Restart the Linkis services to apply the changes
  5. Verify the Spark EngineConn functionality and confirm the RandomStringUtils vulnerability is resolved

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

Fix this in Linkis Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,620
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,792.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39928 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-39928 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