dbcve.org
Command InjectionWeakness · CWE-77

CVE-2024-49194

HIGH · 7.3 CVSS v3.1 Published 2024-12-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable

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
Databricks JDBC Driver 2.x before 2.6.40 could potentially allow remote code execution (RCE) by triggering a JNDI injection via a JDBC URL parameter. The vulnerability is rooted in the improper handling of the krbJAASFile parameter. An attacker could potentially exploit this vulnerability to achieve Remote Code Execution in the context of the driver by tricking a victim into using a crafted connection URL that uses the property krbJAASFile.

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

The Databricks JDBC Driver 2.x before version 2.6.40 contains a JNDI injection vulnerability in the krbJAASFile parameter handling within JDBC connection URLs. An attacker can craft a malicious JDBC URL containing a specially crafted krbJAASFile parameter that triggers JNDI lookup to an attacker-controlled LDAP or similar service, leading to arbitrary code execution in the context of the JDBC driver process.

MitigationUpgrade the Databricks JDBC Driver to version 2.6.40 or later. Additionally, enforce strict validation of JDBC connection URLs and avoid accepting krbJAASFile or other security-sensitive parameters from untrusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/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 the installed Databricks JDBC Driver version
    Inspect the JAR file manifest (META-INF/MANIFEST.MF) or check the driver version via classpath dependencies (e.g., look for databricks-jdbc.jar in your lib directory and check its version metadata)
    Affected if The driver version is 2.x and less than 2.6.40 (e.g., 2.6.30, 2.6.35, etc.)
  2. Search for JDBC connection strings using the krbJAASFile parameter
    Search your application source code, configuration files, and logs for JDBC URLs that contain 'krbJAASFile' (case-insensitive)
    Affected if Any JDBC connection URL includes the krbJAASFile parameter with values from untrusted or external sources
  3. Determine if JDBC URLs are constructed from untrusted input
    Review code paths where JDBC connection URLs are built; trace if user-provided or externally-sourced data flows into the URL construction, particularly into the krbJAASFile parameter
    Affected if The krbJAASFile parameter value in your connection URLs originates from untrusted input (e.g., user request, external API, configuration from untrusted source)
  4. Verify LDAP/JNDI lookup behavior (if possible in your environment)
    Audit network logs or endpoint monitoring for any outbound LDAP or JNDI connections initiated by the JDBC driver process to unexpected or external hosts
    Affected if The JDBC driver makes outbound LDAP or JNDI requests to hosts you do not control or expect

You are affected if the Databricks JDBC Driver version is 2.x before 2.6.40 AND your application uses the krbJAASFile parameter in JDBC connection URLs, especially when that parameter accepts values from untrusted sources.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the Databricks JDBC Driver to version 2.6.40 or later. Additionally, enforce strict validation of JDBC connection URLs and avoid accepting krbJAASFile or other security-sensitive parameters from untrusted sources.

Recommended fix Moderate confidence

Databricks JDBC Driver 2.6.40 or later

  1. 1. Identify all applications and systems using the Databricks JDBC Driver 2.x
  2. 2. Determine the current version of the Databricks JDBC Driver in use by checking the driver JAR file or dependency management system
  3. 3. Download the Databricks JDBC Driver version 2.6.40 or later from the official Databricks download repository
  4. 4. Replace the existing JDBC driver JAR file with the new version 2.6.40 or later
  5. 5. Verify that all JDBC connection configurations avoid using the krbJAASFile parameter unless absolutely necessary
  6. 6. Test database connectivity and authentication after the driver upgrade
  7. 7. Redeploy updated applications to production environments

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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