dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-45198

HIGH · 8.8 CVSS v3.1 Published 2025-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
insightsoftware Spark JDBC 2.6.21 has a remote code execution vulnerability. Attackers can inject malicious parameters into the JDBC URL, triggering JNDI injection during the process when the JDBC Driver uses this URL to connect to the database. This can further lead to remote code execution.

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

The Spark JDBC driver version 2.6.21 is vulnerable to JNDI injection via malicious parameters embedded in JDBC connection URLs. When the driver processes these crafted URLs during database connection establishment, it can be coerced into performing JNDI lookups to attacker-controlled endpoints, enabling remote code execution.

MitigationUpgrade to a patched version of insightsoftware Spark JDBC driver and ensure JDBC URL parameters are validated/sanitized to prevent injection of malicious JNDI lookup strings.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Locate Spark JDBC driver JAR files
    Search for JAR files containing 'spark' and 'jdbc' in your application dependencies, lib folders, or classpath. Common patterns: spark-jdbc_*.jar, spark-sql_*.jar, or vendor-specific bundles. Use commands like 'find / -name "*spark*jdbc*.jar"' or inspect your build manifest/Maven/Gradle dependencies.
    Affected if A Spark JDBC driver JAR file exists in your environment's classpath or library directories.
  2. Determine driver version
    Inspect the JAR file metadata: check META-INF/MANIFEST.MF for 'Implementation-Version' or 'Specification-Version', or examine the filename which often includes the version. Alternatively, query the driver programmatically via DriverManager.getDriver().getMajorVersion()/.getMinorVersion()/.getDriverVersion().
    Affected if The driver version is 2.6.21 or falls within any additional vulnerable version ranges identified in official advisories.
  3. Identify JDBC connection URL usage
    Search configuration files (application.properties, XML configs, environment variables), log files, and source code for JDBC connection strings starting with: jdbc:spark://, jdbc:hive2:// (when using Spark thrift server), or vendor-specific Spark JDBC URL patterns.
    Affected if JDBC connection URLs pointing to Spark databases or Spark Thrift Server are configured or used in your application.
  4. Check for dynamic URL construction
    Review code that builds JDBC URLs programmatically, looking for string concatenation or parameter interpolation from user input, external config, or untrusted sources. Search for patterns like 'jdbc:spark://...?' being assembled at runtime.
    Affected if JDBC URLs are constructed dynamically with parameters that could be influenced by external input.
  5. Inspect runtime driver loading
    Run your application and examine loaded classes via 'jcmd <pid> GC.class_histogram' or debugging tools, filtering for 'org.apache.spark.sql' or 'com.simba.spark' driver classes. Check logs for driver initialization messages.
    Affected if The Spark JDBC driver is loaded and actively used at runtime.

You are affected if the Spark JDBC driver version 2.6.21 (or another vulnerable version) is present in your environment AND JDBC connection URLs are being processed, which would allow attacker-controlled JNDI lookup strings to trigger remote code execution.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of insightsoftware Spark JDBC driver and ensure JDBC URL parameters are validated/sanitized to prevent injection of malicious JNDI lookup strings.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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