WaratekVRT Sign in

CVE-2024-23953 Apache Hive

Affected softwareApache Hive
Severity6.5 Medium CVSS 3.1
Fixed in4.0.0
WeaknessCWE-208
Published28 Jan 2025
Updated17 Jun 2026

Description

Use of Arrays.equals() in LlapSignerImpl in Apache Hive to compare message signatures allows attacker to forge a valid signature for an arbitrary message byte by byte. The attacker should be an authorized user of the product to perform this attack. Users are recommended to upgrade to version 4.0.0, which fixes this issue. The problem occurs when an application doesn’t use a constant-time algorithm for validating a signature. The method Arrays.equals() returns false right away when it sees that one of the input’s bytes are different. It means that the comparison time depends on the contents of the arrays. This little thing may allow an attacker to forge a valid signature for an arbitrary message byte by byte. So it might allow malicious users to submit splits/work with selected signatures to LLAP without running as a privileged user, potentially leading to DDoS attack. More details in the reference section.

CWE-290

Exploitation status

No public exploit

No exploit has been reported in the sources we check. Published a year ago.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment exploitation: none
  • Indexed PoC none indexed
  • EPSS 1.4% chance in 30 days

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists: apache/hive b418e3c.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active
Decided by Medium or Low severity, no CISA or VulnCheck KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory
Finding This CVE is MEDIUM severity, is not listed in CISA KEV or VulnCheck KEV, has no public exploit or PoC in any indexed source, carries no CISA Vulnrichment finding of a demonstrated exploit, and is not part of an Oracle Critical Patch Update. None of the signals that would put it in front of an engineer is present, and the volume of CVEs below that bar is too great to take one at a time, so no rule is written for it. This is a decision about what we act on, not a finding that the CVE is harmless — a patch may well be derivable, and a low-severity defect can still be one link in a longer chain.
Candidate fix https://github.com/apache/hive/commit/b418e3c9f479ba8e7d31e6470306111002ffa809 : a commit: the change itself

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev
PackageIntroducedFixedLast affected
org.apache.hive:hive-llap-common 0 4.0.0 unbounded

Products and versions

2 products, 2 version entries
SourceVendorProductSchemeAffected versions
nvd apache hive generic ≥ 2.2.0 and < 4.0.0
osv org.apache.hive hive-llap-common generic < 4.0.0

References

URLTags
https://github.com/apache/hive/commit/b418e3c9f479ba8e7d31e6470306111002ffa809 commit
https://blog.gypsyengineer.com/en/security/preventing-timing-attacks-with-codeql.html WEB
https://cqr.company/web-vulnerabilities/timing-attacks WEB
https://github.com/apache/hive PACKAGE
https://issues.apache.org/jira/browse/HIVE-28030 WEB
https://lists.apache.org/thread/0nloywj49nbtlc6l3c6363qvq7o1ztb7 WEB
http://www.openwall.com/lists/oss-security/2025/01/28/3 WEB
https://cqr.company/web-vulnerabilities/timing-attacks/ Technical Description

Timeline

Published2025-01-28By the CVE Program.
NVD record modified2026-06-17NVD's own last-modified date for this record.