Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

n/a · Vulnerability

cve-program · severity unknowneuvd · severity unknownCVSS 3.1 · [email protected] · Primary 7.4 HIGHCVSS 2.0 · [email protected] · Primary 5.8 MEDIUMCVSS_V3 Publisher rating HIGHFixed by github.com/hashicorp/vault 1.7.2Fixed by github.com/hashicorp/vault 1.6.5Fixed by github.com/hashicorp/vault 1.5.9osv · severity unknownFixed by github.com/hashicorp/vault 1.5.9Fixed by github.com/hashicorp/vault 1.6.5Fixed by github.com/hashicorp/vault 1.7.2KEV status unknown

cve-program · CVE-2021-32923

Published

HashiCorp Vault and Vault Enterprise allowed the renewal of nearly-expired token leases and dynamic secret leases (specifically, those within 1 second of their maximum TTL), which caused them to be incorrectly treated as non-expiring during subsequent use. Fixed in 1.5.9, 1.6.5, and 1.7.2.

Read the publisher's advisory

euvd · EUVD-2021-1251

Published

HashiCorp Vault and Vault Enterprise allowed the renewal of nearly-expired token leases and dynamic secret leases (specifically, those within 1 second of their maximum TTL), which caused them to be incorrectly treated as non-expiring during subsequent use. Fixed in 1.5.9, 1.6.5, and 1.7.2.

Read the publisher's advisory

nvd · CVE-2021-32923

Published

HashiCorp Vault and Vault Enterprise allowed the renewal of nearly-expired token leases and dynamic secret leases (specifically, those within 1 second of their maximum TTL), which caused them to be incorrectly treated as non-expiring during subsequent use. Fixed in 1.5.9, 1.6.5, and 1.7.2.

Read the publisher's advisory

osv · GHSA-38j9-7pp9-2hjw

Published

HashiCorp Vault and Vault Enterprise allowed the renewal of nearly-expired token leases and dynamic secret leases (specifically, those within 1 second of their maximum TTL), which caused them to be incorrectly treated as non-expiring during subsequent use. Fixed in 1.5.9, 1.6.5, and 1.7.2.

Read the publisher's advisory

osv · GO-2022-0623

Published

Invalid session token expiration in github.com/hashicorp/vault

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2021-32923

Published

n/a

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "product": "n/a",
                    "vendor": "n/a",
                    "versions": [
                        {
                            "status": "affected",
                            "version": "n/a"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2021-1251

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Jun 3, 2021, 10:38:26 AM

dateUpdated: Aug 3, 2024, 11:33:56 PM

1 related source bulletins · separate from aliases

msrc_CVE-2021-32923: HashiCorp Vault and Vault Enterprise allowed the renewal of nearly-expired token leases and dynamic secret leases (specifically those within 1 second of their maximum TTL) which caused them to be incorrectly treated as non-expiring during subsequent use. Fixed in 1.5.9 1.6.5 and 1.7.2.

CVE-2021-32923

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2021-32923

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-613

Original publisher date fields

published: 2021-06-03T11:15:08.737

lastModified: 2026-06-17T03:53:48.407

2 source CPE criteria · context only
  • cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:*
  • cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-38j9-7pp9-2hjw

Published

github.com/hashicorp/vault

Go

SEMVER · introduced 1.7.0 → fixed 1.7.2

github.com/hashicorp/vault

Go

SEMVER · introduced 1.6.0 → fixed 1.6.5

github.com/hashicorp/vault

Go

SEMVER · introduced 0.10.0 → fixed 1.5.9

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2022-0623

Published

github.com/hashicorp/vault

Go

SEMVER · introduced 0.10.0 → fixed 1.5.9 → introduced 1.6.0 → fixed 1.6.5 → introduced 1.7.0 → fixed 1.7.2

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 05:53 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current