dbcve.org
HiveApplication · Apache

CVE-2024-23945

MEDIUM · 5.9 CVSS v3.1 Published 2024-12-23
Fix available
A fix is available. Upgrade to 3.3.4 / 3.4.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Public exploit Remotely reachable No privileges Zero-click Patch available

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
Signing cookies is an application security feature that adds a digital signature to cookie data to verify its authenticity and integrity. The signature helps prevent malicious actors from modifying the cookie value, which can lead to security vulnerabilities and exploitation. Apache Hive’s service component accidentally exposes the signed cookie to the end user when there is a mismatch in signature between the current and expected cookie. Exposing the correct cookie signature can lead to further exploitation. The vulnerable CookieSigner logic was introduced in Apache Hive by HIVE-9710 (1.2.0) and in Apache Spark by SPARK-14987 (2.0.0). The affected components are the following: * org.apache.hive:hive-service * org.apache.spark:spark-hive-thriftserver_2.11 * org.apache.spark:spark-hive-thriftserver_2.12

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

A detailed technical summary for this CVE is being prepared.

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:>= 1.2.0, < 4.0.0
SparkApplication
Affected:>= 2.0.0, < 3.3.4>= 3.4.0, < 3.4.2= 3.5.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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

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 3.3.4 / 3.4.2 / 4.0.0 or later
Fixed in 3.3.43.4.24.0.0
Vendor patch github.com →
Recommended fix High confidence

Hive: 4.0.0+ | Spark: 3.3.4+, 3.4.2+, or 3.5.1+

  1. 1. Identify which affected component(s) are in use: org.apache.hive:hive-service, org.apache.spark:spark-hive-thriftserver_2.11, or org.apache.spark:spark-hive-thriftserver_2.12
  2. 2. For Apache Hive users: Upgrade hive-service to version 4.0.0 or later
  3. 3. For Apache Spark users using spark-hive-thriftserver: Upgrade to version 3.3.4 or later, OR 3.4.2 or later, OR a version greater than 3.5.0
  4. 4. After upgrading, verify that the cookie signing error messages no longer expose the signed cookie value
  5. 5. Test authentication and session management functionality to ensure the fix does not break legitimate cookie validation
Caveat Hive 4.0.0 is a major version upgrade with significant changes; review Hive 4.0.0 release notes for breaking changes before upgrading

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $900. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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