dbcve.org
LinkisApplication · Apache

CVE-2025-59355

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-19
Fix available
A fix is available. Upgrade to 1.8.0 or later.
See remediation →
71/100
Remediation priority · Elevated
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
A vulnerability. When org.apache.linkis.metadata.util.HiveUtils.decode() fails to perform Base64 decoding, it records the complete input parameter string in the log via logger.error(str + "decode failed", e). If the input parameter contains sensitive information such as Hive Metastore keys, plaintext passwords will be left in the log files when decoding fails, resulting in information leakage. Affected Scope Component: Sensitive fields in hive-site.xml (e.g., javax.jdo.option.ConnectionPassword) or other fields encoded in Base64. Version: Apache Linkis 1.0.0 – 1.7.0 Trigger Conditions The value of the configuration item is an invalid Base64 string. Log files are readable by users other than hive-site.xml administrators. Severity: Low The probability of Base64 decoding failure is low. The leakage is only triggered when logs at the Error level are exposed. Remediation Apache Linkis 1.8.0 and later versions have replaced the log with desensitized content. logger.error("URL decode failed: {}", e.getMessage()); // 不再输出 str Users are recommended to upgrade to version 1.8.0, which fixes the 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 · high confidence

In Apache Linkis versions 1.0.0-1.7.0, the HiveUtils.decode() method logs the full input parameter string when Base64 decoding fails, which can expose sensitive Hive Metastore credentials (like javax.jdo.option.ConnectionPassword) in plaintext to log files readable by non-admin users.

MitigationUpgrade to Apache Linkis 1.8.0 or later, which replaces the unsafe log statement with desensitized output that only logs the error message without the input string.

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.0.0, < 1.8.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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Apache Linkis version
    Check the installed Linkis version (for example, look for a version file, pom.xml, or the actual jar file names in the installation directory). Compare it against the affected range: 1.0.0 to 1.7.0.
    Affected if Version is 1.0.0 through 1.7.0 inclusive.
  2. Determine if Hive is configured
    Check if Linkis is configured to connect to Hive Metastore by reviewing the Linkis configuration files (typically in conf/ or the deployment configuration) for Hive-related settings such as hive.metastore.uris or javax.jdo.option.ConnectionPassword.
    Affected if Hive Metastore credentials are configured in Linkis.
  3. Inspect log files for exposed credentials
    Search Linkis log directories (commonly found under logs/ or the configured log path) for plaintext occurrences of the string javax.jdo.option.ConnectionPassword or any Base64-encoded values that decode to Hive passwords. Use grep or a log analysis tool to scan for these patterns.
    Affected if The connection password appears in plaintext in any log file.
  4. Verify log file permissions
    Check the file permissions on Linkis log files to determine if they are readable by non-admin users or users outside the Linkis administrator group.
    Affected if Log files are world-readable or readable by non-admin users.

You are affected if you run Apache Linkis 1.0.0-1.7.0 with Hive configured, and your log files contain plaintext Hive credentials or are accessible to non-admin users.

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.8.0 or later
Fixed in 1.8.0
Interim mitigation

Upgrade to Apache Linkis 1.8.0 or later, which replaces the unsafe log statement with desensitized output that only logs the error message without the input string.

Recommended fix High confidence

1.8.0

  1. Upgrade Apache Linkis to version 1.8.0 or later to receive the patch that replaces logger.error(str + "decode failed", e) with logger.error("URL decode failed: {}", e.getMessage())

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

Fix this in Linkis Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $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 $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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