dbcve.org
LinkisApplication · Apache

CVE-2023-50740

MEDIUM · 5.3 CVSS v3.1 Published 2024-03-06
Fix available
A fix is available. Upgrade to 1.5.0 or later.
See remediation →
62/100
Remediation priority · Elevated
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.4.0, The password is printed to the log when using the Oracle data source of the Linkis data source module.  We recommend users upgrade the version of Linkis to version 1.5.0

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.4.0 and earlier, the Oracle data source module logs database passwords in plaintext when establishing connections. This exposes sensitive credentials through log files, potentially allowing unauthorized access to the Oracle databases.

MitigationUpgrade Apache Linkis to version 1.5.0 or later. Review and rotate any Oracle database passwords that may have been exposed in logs.

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.5.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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Apache Linkis version by reviewing the version file, build configuration, or using the Linkis administration interface. Common locations include version metadata files in the installation directory or the pom.xml if source is available.
    Affected if The installed version is 1.4.0 or earlier (any version below 1.5.0)
  2. Locate Oracle data source configurations
    Search for Oracle datasource configuration files in the Linkis configuration directories. Look for files containing Oracle connection parameters such as jdbc:oracle URLs, datasource definitions, or connection pool configurations.
    Affected if Oracle datasource configurations exist and the version is vulnerable
  3. Search log files for plaintext passwords
    Examine Linkis log files (typically found in the logs/ directory of the Linkis installation) for patterns matching plaintext Oracle passwords. Search for strings containing 'password=' or visible password values near Oracle connection establishment messages.
    Affected if Log files contain plaintext Oracle database passwords or password= parameters in connection strings
  4. Verify Oracle connection usage
    Review Linkis database connection settings and datasource definitions to confirm Oracle is being used as a data source. Check datasource management configurations or property files for Oracle JDBC connections.
    Affected if Oracle datasource is configured and the Linkis version is below 1.5.0

The environment is affected if Apache Linkis version is below 1.5.0 AND Oracle datasource is configured, with plaintext passwords potentially visible in log files.

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.5.0 or later
Fixed in 1.5.0
Interim mitigation

Upgrade Apache Linkis to version 1.5.0 or later. Review and rotate any Oracle database passwords that may have been exposed in logs.

Recommended fix High confidence

1.5.0

  1. 1. Review the Apache Linkis 1.5.0 release notes and upgrade documentation
  2. 2. Create a complete backup of the current Linkis installation including configuration files and databases
  3. 3. Stop all Linkis services gracefully
  4. 4. Upgrade the Linkis installation to version 1.5.0 following the standard upgrade procedure
  5. 5. Verify that the Oracle data source connection no longer logs passwords by checking the log files
  6. 6. Start Linkis services and confirm normal operation
Caveat Review release notes for any configuration or API changes between your current version and 1.5.0

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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