CVE-2024-23945

Info Disclosure in Apache Spark 2.0.0 – 3.3.4

Public PoCInfo Disclosure

Published

23 December 2024

Modified

14 July 2025

Patch / advisory

View advisory

CVSS Score v3.1 5.9

Click a component to see what it means

Raw vector

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

EPSS Score 0.015 72th percentile

Risk Priority 54 floored blend · peak EPSS

Summary

CVE-2024-23945 is a medium-severity Generation of Error Message Containing Sensitive Information (CWE-209) vulnerability in Apache Spark. Its CVSS base score is 5.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Software (T1592.002); ranked in the top 28% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-11 (Error Handling) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-23945 affects the cookie signing logic in Apache Hive’s service component (org.apache.hive:hive-service) and the corresponding Spark Hive Thriftserver modules (spark-hive-thriftserver_2.11 and _2.12). The flaw, introduced by HIVE-9710 in Hive 1.2.0 and SPARK-14987 in Spark 2.0.0, causes the correct signed cookie value to be returned to a client whenever a signature mismatch occurs between the supplied and expected cookie, exposing the signature that is otherwise intended to protect integrity.

An unauthenticated remote attacker can trigger the mismatch condition over the network to obtain a valid cookie signature. With the signature in hand, the attacker can forge or modify subsequent cookies, achieving integrity violations that the signing mechanism was designed to prevent. The CVSS 5.9 rating reflects the high attack complexity required to reach this outcome despite the absence of required credentials.

Public references point to corrective commits in the Hive and Spark repositories that address the exposure in the CookieSigner path. The EPSS score reached a peak of 0.0852 after disclosure, indicating a measurable increase in observed exploitation interest from an initially low baseline.

OWASP Top 10 for Web (2025)

EU & UK References

🇪🇺 ENISA EUVD: EUVD-2024-3564

Vulnerability Data

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

CWE(s): CWE-209

Related Threats

MITRE ATT&CK Enterprise Techniques

T1592.002 Software Reconnaissance

Adversaries may gather information about the victim's host software that can be used during targeting.

attack.mitre.org →

T1082 System Information Discovery Discovery

An adversary may attempt to get detailed information about the operating system and hardware, including version, patches, hotfixes, service packs, and architecture.

attack.mitre.org →

T1592 Gather Victim Host Information Reconnaissance

Adversaries may gather information about the victim's hosts that can be used during targeting.

attack.mitre.org →

T1595 Active Scanning Reconnaissance

Adversaries may execute active reconnaissance scans to gather information that can be used during targeting.

attack.mitre.org →

Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-21733Same vendor: Apache

CVE-2024-45384Same vendor: Apache

CVE-2023-39264Same vendor: Apache

CVE-2026-56139Same vendor: Apache

CVE-2024-53948Same vendor: Apache

CVE-2024-27315Same vendor: Apache

CVE-2026-49365Same vendor: Apache

CVE-2023-25956Same vendor: Apache

CVE-2023-25695Same vendor: Apache

CVE-2025-65995Same vendor: Apache

Affected Assets

apache

hive

1.2.0 — 4.0.0

apache

spark

3.5.0 · 2.0.0 — 3.3.4 · 3.4.0 — 3.4.2

Mitigating Controls

Control response

Prevent

Stop it (NIST 800-53)

—

Detect

Catch it (NIST detect / respond)

—

Harden

Shrink the surface (DISA STIG)

—

Validate

Prove the fix (OWASP ASVS)

V16.5.1

Mitigating Controls (NIST 800-53 r5) AI

SI-11 Error Handling good match

si-11 directly requires error messages to avoid revealing exploitable information about the system or its data.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match

prevents

Secure SDLC practices directly require sanitized error handling to prevent sensitive data disclosure.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.28 Secure coding mostly match

prevents

Secure coding standards explicitly forbid exposing sensitive data in errors.

A.8.29 Security testing in development and acceptance mostly match

finds

Security testing can detect error messages that leak sensitive information.

A.8.15 Logging partial match

degrades

Logging policy can require suppression of sensitive data in error messages.

A.8.25 Secure development life cycle partial match

prevents

Secure SDLC mandates error-handling rules that avoid leaking sensitive information.