CVE intelligence and bounded remediation
CVE-2020-1926 — Apache Hive cookie signature verification used a non constant time comparison which is known to be vulnerable to timing attacks
Medium
CVSS 5.9
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
- Severity
- Medium
- CVSS
- 5.9 (3.1)
- Published
- 2021-03-16
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-208, CWE-203
Affected products
- apache / hive
Matched remediation archetype
Information disclosure and sensitive data exposure
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Trace sensitive data through responses, errors, logs, metrics, traces, caches, exports, files, backups, and client bundles.
- Identify affected subjects, tenants, retention windows, access controls, and downstream copies without opening unnecessary sensitive records.
- Review metadata, timing, status, length, and existence signals as well as direct content disclosure.
Remediate safely
- Minimize collection and output, apply field-level authorization and redaction at a centralized boundary, and return generic external errors.
- Remove secrets and sensitive data from logs, artifacts, URLs, caches, and client-side bundles; rotate credentials that may have been exposed.
- Update the affected component and add synthetic-data tests for response, error, observability, and export paths.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.