Advisory record · GHSA-77pm-w3hx-f8mj

Apache Hive and Spark: CookieSigner exposes the correct signature when message verification fails

CVSS 5.9 MediumEPSS 0.015 · 75th percentile

Published by the GitHub Advisory Database at 23 Dec 2024, 18:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.hive:hive-serviceMaven>=1.2.0, <4.0.04.0.0
org.apache.spark:spark-hive-thriftserver_2.11Maven<=2.4.8No fixed version yet
org.apache.spark:spark-hive-thriftserver_2.12Maven<3.4.23.4.2
Identifiers
GHSA-77pm-w3hx-f8mj · CVE-2024-23945
Weakness (CWE)
CWE-209
Published
23 Dec 2024
Updated
26 Dec 2024

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache Hive's hive-service (versions 1.2.0 up to 4.0.0) and Spark's spark-hive-thriftserver_2.11 (up to 2.4.8, no fix listed) and spark-hive-thriftserver_2.12 (before 3.4.2) expose the correct cookie signature to the end user when signature verification fails. An attacker who can send requests to the service can obtain the valid signature and may use it to further exploit the application. Upgrade hive-service to 4.0.0 or spark-hive-thriftserver_2.12 to 3.4.2; no fix is listed for spark-hive-thriftserver_2.11.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.9 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.015, the 75th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:12 UTC First seen by agentprime
  2. 31 Oct 2026, 15:12 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.