dbcve.org
DorisApplication · Apache

CVE-2024-27438

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-21
Fix available
A fix is available. Upgrade to 2.0.5 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
Download of Code Without Integrity Check vulnerability in Apache Doris. The jdbc driver files used for JDBC catalog is not checked and may resulting in remote command execution. Once the attacker is authorized to create a JDBC catalog, he/she can use arbitrary driver jar file with unchecked code snippet. This code snippet will be run when catalog is initializing without any check. This issue affects Apache Doris: from 1.2.0 through 2.0.4. Users are recommended to upgrade to version 2.0.5 or 2.1.x, 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

Apache Doris JDBC catalog feature does not validate integrity of JDBC driver JAR files, allowing authenticated users with catalog creation privileges to supply malicious JARs containing arbitrary code that executes during catalog initialization.

MitigationUpgrade Apache Doris to version 2.0.5 or 2.1.x. Until then, restrict JDBC catalog creation privileges to trusted administrators only.

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
DorisApplication
Affected:>= 1.2.0, < 2.0.5

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 Doris version
    Run 'select version();' in the Doris BE or FE mysql client, or check the fe.jar/be.jar file version in the installation directory
    Affected if The installed version is >= 1.2.0 and < 2.0.5
  2. Determine if JDBC catalog is in use
    Query 'SHOW CATALOGS;' or check for catalog configuration files in the fe/conf/ or custom_conf/ directories containing 'jdbc' in the connection string
    Affected if Any JDBC catalog is configured and the Doris version is in the affected range
  3. Inspect JDBC driver JAR locations
    Search for JAR files in the fe/plugin/catalog/ directory or any custom plugin path referenced in the catalog definition
    Affected if Non-standard or custom JAR files are present in the JDBC catalog driver path that were not supplied by the Doris distribution
  4. Check catalog creation privileges
    Run 'SHOW GRANTS;' for non-admin users, or query the user_privitlies table to identify users with CATALOG creation privileges
    Affected if Non-admin users have CATALOG_PRIV or CREATE CATALOG privileges in a version within the affected range
  5. Review recent catalog creation activity
    Examine audit logs or query the operation_log table for recent CREATE CATALOG statements, especially those using the JDBC type
    Affected if JDBC catalogs were recently created by non-admin users in an affected version

You are affected if running Apache Doris version 1.2.0 through 2.0.4 (exclusive) and any JDBC catalog is configured, especially if untrusted users have catalog creation privileges.

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 2.0.5 or later
Fixed in 2.0.5
Interim mitigation

Upgrade Apache Doris to version 2.0.5 or 2.1.x. Until then, restrict JDBC catalog creation privileges to trusted administrators only.

Recommended fix High confidence

2.0.5 or 2.1.x

  1. 1. Back up your current Apache Doris installation, configuration files, and databases
  2. 2. Download Apache Doris version 2.0.5 or 2.1.x from the official Apache Doris repository (https://doris.apache.org/download/)
  3. 3. Stop the running Apache Doris service on all nodes
  4. 4. Replace the old Doris installation files with the new version 2.0.5 or 2.1.x
  5. 5. Review configuration files for compatibility with the new version
  6. 6. Restart the Apache Doris service on all nodes
  7. 7. Verify that JDBC catalog functionality works correctly and the vulnerability is resolved
Caveat Major version upgrade from 1.x to 2.x may have breaking changes; review release notes for compatibility considerations

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

Fix this in Doris Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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