Skip to content

Token leases could outlive their TTL in HashiCorp Vault

Critical severity GitHub Reviewed Published May 24, 2022 to the GitHub Advisory Database • Updated Feb 1, 2024

Package

gomod github.com/hashicorp/vault (Go)

Affected versions

>= 1.0, < 1.5.4

Patched versions

1.5.4
Published by the National Vulnerability Database Sep 30, 2020
Published to the GitHub Advisory Database May 24, 2022
Reviewed Feb 1, 2024
Last updated Feb 1, 2024

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.065%
(30th percentile)

Weaknesses

CVE ID

CVE-2020-25816

GHSA ID

GHSA-57gg-cj55-q5g2

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.