dbcve.org
HiveApplication · Apache

CVE-2023-35701

MEDIUM · 6.6 CVSS v3.1 Published 2024-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable 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
Improper Control of Generation of Code ('Code Injection') vulnerability in Apache Hive. The vulnerability affects the Hive JDBC driver component and it can potentially lead to arbitrary code execution on the machine/endpoint that the JDBC driver (client) is running. The malicious user must have sufficient permissions to specify/edit JDBC URL(s) in an endpoint relying on the Hive JDBC driver and the JDBC client process must run under a privileged user to fully exploit the vulnerability.  The attacker can setup a malicious HTTP server and specify a JDBC URL pointing towards this server. When a JDBC connection is attempted, the malicious HTTP server can provide a special response with customized payload that can trigger the execution of certain commands in the JDBC client.This issue affects Apache Hive: from 4.0.0-alpha-1 before 4.0.0. Users are recommended to upgrade to version 4.0.0, 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

Code injection vulnerability in Apache Hive's JDBC driver where a malicious HTTP server can be specified in a JDBC URL. When the JDBC client attempts to connect, the malicious server responds with a crafted payload that can trigger arbitrary command execution on the client machine, requiring the client to run under a privileged user for full exploitation.

MitigationUpgrade the Apache Hive JDBC driver to version 4.0.0 or later to resolve the code injection vulnerability. Restrict permissions for users who can specify/edit JDBC connection URLs and avoid running JDBC client processes under privileged accounts.

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
HiveApplication
Affected:= 4.0.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
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/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 Hive JDBC driver version
    Locate the Hive JDBC driver JAR file (typically named hive-jdbc*.jar or similar) in your classpath or application lib directory. Check the manifest or filename for version information, or use: jar tf hive-jdbc-*.jar | grep manifest
    Affected if The driver version is exactly 4.0.0 (the single affected version) or if you cannot confirm a version different from 4.0.0
  2. Review JDBC URL sources in your application
    Search your codebase for JDBC connection string construction, particularly looking for URLs passed from external input, configuration files, or user-facing fields. Look for patterns like DriverManager.getConnection() with URLs derived from request parameters, environment variables, or config files
    Affected if JDBC URLs can be influenced by untrusted users or external sources without validation
  3. Audit process privileges for JDBC clients
    Identify all processes or applications that establish Hive JDBC connections. Check the OS user account or service account under which these processes run using commands like: ps aux | grep -i hive or whoami for the executing user
    Affected if The JDBC client process runs under a privileged account (root, administrator, or any account with elevated system permissions)
  4. Check for HTTP-based Hive connections
    Inspect your JDBC connection URLs for the transport mode parameter, typically ?serviceDiscoveryMode=zooKeeper; or look for hive2:// URLs. Identify if HTTP transport is in use which enables the malicious server vector
    Affected if Your JDBC URL uses HTTP transport mode to connect to Hive servers

You are affected if you use Apache Hive JDBC driver version 4.0.0 and either allow untrusted input to define JDBC URLs or run JDBC client processes under privileged accounts.

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 Apache Hive JDBC driver to version 4.0.0 or later to resolve the code injection vulnerability. Restrict permissions for users who can specify/edit JDBC connection URLs and avoid running JDBC client processes under privileged accounts.

Recommended fix High confidence

Apache Hive 4.0.0

  1. 1. Identify all systems running the Apache Hive JDBC driver version 4.0.0-alpha-1 or later but prior to 4.0.0
  2. 2. Download Apache Hive version 4.0.0 from the official Apache Hive release repository (e.g., Apache archives)
  3. 3. Replace the vulnerable hive-jdbc*.jar files with the version 4.0.0 JAR files on all affected client machines
  4. 4. Ensure JDBC connection configurations are updated to use the new driver if necessary
  5. 5. Restart any applications or services that use the Hive JDBC driver to load the updated library
  6. 6. Verify the upgrade by testing JDBC connection functionality

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

Fix this in Hive Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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