dbcve.org
VaultApplication · Hashicorp

CVE-2022-41316

MEDIUM · 5.3 CVSS v3.1 Published 2022-10-12
Fix available
A fix is available. Upgrade to 1.9.10 / 1.10.7 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
HashiCorp Vault and Vault Enterprise’s TLS certificate auth method did not initially load the optionally configured CRL issued by the role's CA into memory on startup, resulting in the revocation list not being checked if the CRL has not yet been retrieved. Fixed in 1.12.0, 1.11.4, 1.10.7, and 1.9.10.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The TLS certificate authentication method in HashiCorp Vault did not load the optionally configured CRL (Certificate Revocation List) from the role's CA into memory on startup. This resulted in the revocation list not being checked until the CRL had been retrieved at least once, potentially allowing authentication with revoked certificates.

MitigationUpgrade Vault to version 1.12.0, 1.11.4, 1.10.7, or 1.9.10 (or later) to ensure the CRL is properly loaded on startup. Prior to upgrading, audit TLS cert auth configurations and ensure a maintenance window for the upgrade.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
VaultApplication
Affected:< 1.9.10>= 1.10.0, < 1.10.7>= 1.11.0, < 1.11.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Vault version
    Run `vault version` or inspect the Vault binary/process to determine the installed version
    Affected if The version is < 1.9.10, or >= 1.10.0 and < 1.10.7, or >= 1.11.0 and < 1.11.4
  2. Verify TLS certificate authentication is enabled
    Run `vault auth list` to see all enabled auth methods and confirm 'cert' is listed as an enabled method
    Affected if TLS cert auth (cert) is not mounted or enabled - the CVE only applies when this method is in use
  3. List TLS cert auth roles
    Run `vault list auth/cert/certs` to enumerate configured certificate roles
    Affected if No roles are configured - the vulnerability only applies when at least one TLS cert role exists
  4. Check role for CRL configuration
    Run `vault read auth/cert/certs/<role_name>` for each role and look for `crl` or `revoke_from_crl` fields
    Affected if The role has no CRL configured (no `crl` field set) - the flaw only matters when a CRL is supposed to be used but not loaded on startup
  5. Verify CRL has been retrieved at least once
    This condition is transient - the vulnerability exists until the CRL is fetched for the first time after Vault startup. Check Vault logs for successful CRL retrieval calls to the CA, or monitor the next authentication attempt that triggers CRL download
    Affected if Vault has not yet fetched the CRL since startup - revoked certificates could be accepted until the first CRL retrieval occurs

A user is affected if: Vault version is in the affected range, TLS cert auth is enabled with at least one configured role that includes CRL settings, and the Vault instance has not yet retrieved the CRL since its last startup.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.9.10 / 1.10.7 / 1.11.4 or later
Fixed in 1.9.101.10.71.11.4
Interim mitigation

Upgrade Vault to version 1.12.0, 1.11.4, 1.10.7, or 1.9.10 (or later) to ensure the CRL is properly loaded on startup. Prior to upgrading, audit TLS cert auth configurations and ensure a maintenance window for the upgrade.

Recommended fix High confidence

1.12.0 (recommended) or 1.11.4, 1.10.7, 1.9.10 as appropriate for your version branch

  1. 1. Backup your Vault data and configuration using `vault operator raft snapshot save` or your existing backup mechanism
  2. 2. Review the Vault upgrade documentation at https://www.vaultproject.io/docs/upgrading
  3. 3. Download the appropriate fixed version (1.12.0, 1.11.4, 1.10.7, or 1.9.10) from https://www.vaultproject.io/downloads
  4. 4. Stop the Vault service gracefully
  5. 5. Replace the Vault binary with the new version
  6. 6. Start the Vault service
  7. 7. Verify the TLS certificate auth method now properly loads the CRL on startup
  8. 8. Test certificate revocation behavior to confirm the fix is working
Caveat Standard Vault upgrade notes apply - review breaking changes in the version-specific upgrade guides; no changes specific to this security fix

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vault Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41316 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41316 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data