Summary
Apache Hive and Spark: CookieSigner exposes the correct signature when message verification fails
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
Impact
CVE-2024-23945 has a CVSS score of 5.9 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.0.0, 3.4.2); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
org.apache.hive:hive-service to 4.0.0 or later; org.apache.spark:spark-hive-thriftserver_2.12 to 3.4.2 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2024-23945? CVE-2024-23945 is a high-severity security vulnerability in org.apache.hive:hive-service (maven), affecting versions >= 1.2.0, < 4.0.0. It is fixed in 4.0.0, 3.4.2.
- How severe is CVE-2024-23945? CVE-2024-23945 has a CVSS score of 5.9 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2024-23945?
org.apache.hive:hive-service(maven) (versions >= 1.2.0, < 4.0.0)org.apache.spark:spark-hive-thriftserver_2.11(maven) (versions <= 2.4.8)org.apache.spark:spark-hive-thriftserver_2.12(maven) (versions < 3.4.2)
- Is there a fix for CVE-2024-23945? Yes. CVE-2024-23945 is fixed in 4.0.0, 3.4.2. Upgrade to this version or later.
- Is CVE-2024-23945 exploitable, and should I be worried? Whether CVE-2024-23945 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-23945 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-23945?
- Upgrade
org.apache.hive:hive-serviceto 4.0.0 or later - Upgrade
org.apache.spark:spark-hive-thriftserver_2.12to 3.4.2 or later
- Upgrade