CVE-2024-45199
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 · uneditedinsightsoftware Hive JDBC through 2.6.13 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 · moderate confidenceThe Hive JDBC driver through version 2.6.13 is vulnerable to JNDI injection via malicious parameters embedded in JDBC connection URLs. When the driver parses and uses these crafted URLs to establish database connections, it performs unsafe JNDI lookups that can be abused to achieve remote code execution.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Hive JDBC driver presenceSearch your application's classpath, build files (pom.xml, build.gradle), lib directories, or dependency management systems for the Hive JDBC driver (hive-jdbc or hive-jdbc-*.jar)Affected if The Hive JDBC driver JAR file is found in your environment
-
Determine installed driver versionInspect the JAR file metadata or check your dependency management files for the exact version number of the hive-jdbc artifactAffected if The version is 2.6.13 or any earlier version (e.g., 2.6.12, 2.6.0, 1.x)
-
Audit JDBC URL input sourcesReview your application code and configuration to identify where Hive JDBC connection URLs originate - examine database connection configuration, user input handling, API endpoints, or external configuration files that supply JDBC URL parametersAffected if JDBC connection URLs are accepted from untrusted or external sources without validation
-
Inspect active JDBC connection stringsReview your application logs, connection pool configurations, or runtime environment variables for Hive JDBC connection strings; look for patterns containing ldap:, rmi:, or dns: in URL parametersAffected if Active or logged JDBC URLs contain JNDI-related protocols (ldap, rmi, dns) in parameter values
-
Check JVM security settingsInspect your JVM startup arguments or security policy files for the presence and state of com.sun.jndi.ldap.object.trustURLCodebase and related JNDI security propertiesAffected if These JNDI security properties are not set to false or are absent from the JVM configuration
You are affected if you have the Hive JDBC driver version 2.6.13 or earlier in use and your application processes JDBC connection URLs from any source that could contain crafted JNDI injection payloads.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade the Hive JDBC driver to a patched version once released. As a temporary mitigation, restrict JDBC URL input sources and disable JNDI lookup features in the JVM via com.sun.jndi.ldap.object.trustURLCodebase and related properties.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45199 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-45199 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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