dbcve.org
VaultApplication · Hashicorp

CVE-2022-25244

MEDIUM · 6.5 CVSS v3.1 Published 2022-03-10
Fix available
A fix is available. Upgrade to 1.7.10 / 1.8.9 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Vault Enterprise clusters using the tokenization transform feature can expose the tokenization key through the tokenization key configuration endpoint to authorized operators with `read` permissions on this endpoint. Fixed in Vault Enterprise 1.9.4, 1.8.9 and 1.7.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

Vault Enterprise clusters using the tokenization transform feature have an information disclosure vulnerability where the tokenization key can be exposed through the tokenization key configuration endpoint to any authorized operator with `read` permissions on that endpoint. This allows unauthorized access to sensitive cryptographic key material.

MitigationUpgrade Vault Enterprise to version 1.9.4, 1.8.9, or 1.7.10 (or later) to patch the tokenization key exposure. Alternatively, restrict `read` permissions on the tokenization key configuration endpoint until the upgrade is applied.

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.7.0, < 1.7.10>= 1.8.0, < 1.8.9>= 1.9.0, < 1.9.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Confirm you are running Vault Enterprise
    Run `vault version` and check the output for 'ent' or 'enterprise' in the version string. Community edition is not affected by this vulnerability.
    Affected if The output shows 'ent' or 'enterprise' (not just 'vault')
  2. Check installed Vault version against affected ranges
    Run `vault version` and compare the semantic version to: 1.7.0 through 1.7.9, 1.8.0 through 1.8.8, or 1.9.0 through 1.9.3.
    Affected if The version falls within any of these ranges: >=1.7.0 <1.7.10, >=1.8.0 <1.8.9, or >=1.9.0 <1.9.4
  3. Verify tokenization transform feature is in use
    List existing transform transformations using `vault list transform/transformation` (requires appropriate permissions). Look for transformations of type 'tokenization'.
    Affected if Any transformations of type 'tokenization' exist in the Vault secrets engine
  4. Check for read access to tokenization key configuration endpoint
    Review Vault policies or ACLs for any grants of 'read' capability on the path 'transform/tokenization/*/keys' or similar tokenization key configuration endpoints.
    Affected if Any policy or role grants read access on tokenization key configuration paths to operators or applications

If running Vault Enterprise with a version in the affected ranges AND the tokenization transform feature is configured AND operators have read access to the tokenization key configuration endpoint, the environment is vulnerable to key material exposure.

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.7.10 / 1.8.9 / 1.9.4 or later
Fixed in 1.7.101.8.91.9.4
Interim mitigation

Upgrade Vault Enterprise to version 1.9.4, 1.8.9, or 1.7.10 (or later) to patch the tokenization key exposure. Alternatively, restrict `read` permissions on the tokenization key configuration endpoint until the upgrade is applied.

Recommended fix High confidence

Vault Enterprise 1.7.10, 1.8.9, or 1.9.4 depending on current major.minor branch

  1. 1. Identify the current Vault Enterprise version by running `vault version`
  2. 2. Determine which upgrade path applies based on current version: 1.7.x -> 1.7.10, 1.8.x -> 1.8.9, or 1.9.x -> 1.9.4
  3. 3. Review the Vault upgrade guide at https://www.vaultproject.io/docs/upgrading
  4. 4. Take a backup of Vault data following organizational backup procedures
  5. 5. Plan for maintenance window as upgrade will require a restart
  6. 6. Download the appropriate fixed version from https://www.hashicorp.com/products/vault/
  7. 7. Stop the Vault service on all cluster nodes
  8. 8. Install the upgraded Vault binary on all nodes
Caveat Point releases (e.g., 1.9.3 to 1.9.4) typically contain no breaking changes; always review changelogs for full details

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

Fix this in Vault Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25244 — 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-25244 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