# CVE-2020-1926: Timing attack in Cookie signature verification

> Attackers can recover user cookie signatures via timing attacks, potentially leading to account takeover in Apache Hive deployments.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Mar 2021
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-54g4-5cf6-hjp3

## What is CVE-2020-1926?

CVE-2020-1926 is a medium-severity vulnerability in Apache Hive, published on 16 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Apache Hive cookie signature verification used a non constant time comparison which is known to be vulnerable to timing attacks. This could allow recovery of another users cookie signature. The issue was addressed in Apache Hive 2.3.8

Weakness: CWE-203 (Observable Discrepancy), CWE-208 (Observable Timing Discrepancy)

## Which versions are affected by CVE-2020-1926?

2 open source packages ship an affected version, including org.apache.hive:hive. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.hive:hive` | Maven | All versions | 2.3.8 |
| `org.apache.hive:hive` | Maven | All versions | 2.3.8 |

Products: Apache Hive.

## How do I fix CVE-2020-1926?

Upgrade org.apache.hive:hive to 2.3.8 or later.

## Is CVE-2020-1926 being exploited?

There is no known exploitation of CVE-2020-1926 in the wild and no public exploit code.

## Other vulnerabilities in Apache Hive

- [CVE-2026-49845](https://insights.sbomify.com/CVE-2026-49845/): Apache Hive: SQL Injection vulnerability in HiveMetaStore partition-name direct-SQL paths (critical 9.8)
- [CVE-2018-21234](https://insights.sbomify.com/CVE-2018-21234/): Deserialization of Untrusted Data in Jodd (critical 9.8)
- [CVE-2026-55976](https://insights.sbomify.com/CVE-2026-55976/): Apache Hive: SSRF vulnerability in Hive Avro Serde due to Insufficient input validation on avro.schema.url (critical 9.1)
- [CVE-2018-1282](https://insights.sbomify.com/CVE-2018-1282/): SQL Injection in hive-jdbc (critical 9.1)
- [CVE-2022-41137](https://insights.sbomify.com/CVE-2022-41137/): Apache Hive: Deserialization of untrusted data when fetching partitions from the Metastore (high 8.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1926 and fix it if it is affected.

What it is: CVE-2020-1926 is a medium-severity vulnerability in Apache Hive, published on 16 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-1926 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.hive:hive (Maven): affected all versions; fixed in 2.3.8
- org.apache.hive:hive (Maven): affected all versions; fixed in 2.3.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-1926/ (Markdown: https://insights.sbomify.com/CVE-2020-1926/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-1926
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-1926
- OSV: https://osv.dev/vulnerability/CVE-2020-1926

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-1926/
Summaries are generated and may contain mistakes; the official description above is the record.