dbcve.org
VaultApplication · Hashicorp

CVE-2022-36129

CRITICAL · 9.1 CVSS v3.1 Published 2022-07-26
Fix available
A fix is available. Upgrade to after 1.10.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Enterprise 1.7.0 through 1.9.7, 1.10.4, and 1.11.0 clusters using Integrated Storage expose an unauthenticated API endpoint that could be abused to override the voter status of a node within a Vault HA cluster, introducing potential for future data loss or catastrophic failure. Fixed in Vault Enterprise 1.9.8, 1.10.5, and 1.11.1.

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

HashiCorp Vault Enterprise versions 1.7.0-1.9.7, 1.10.4, and 1.11.0 using Integrated Storage expose an unauthenticated API endpoint that allows overriding the voter status of a node within an HA cluster, potentially causing data loss or catastrophic failure.

MitigationUpgrade Vault Enterprise to versions 1.9.8, 1.10.5, 1.11.1 or later. Until upgraded, restrict network access to Vault API endpoints to trusted networks only.

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.9.7>= 1.10.0, <= 1.10.4= 1.11.0

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
High
Availability
High

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

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 Vault Enterprise edition
    Run 'vault version' and check if the output indicates 'ent' or 'enterprise' edition (not open source)
    Affected if Running Vault Enterprise edition
  2. Check installed Vault version
    Run 'vault version' to get the exact version number and compare it to affected ranges: 1.7.0 through 1.9.7, 1.10.4, or 1.11.0
    Affected if Version falls within 1.7.0-1.9.7, 1.10.4, or 1.11.0
  3. Verify Integrated Storage is in use
    Run 'vault operator raft configuration -format=json' or check the storage configuration in Vault config file for 'storage "raft"' backend
    Affected if Integrated Storage (Raft) is configured as the storage backend
  4. Check API endpoint accessibility
    From an untrusted network perspective, attempt a GET request to /v1/sys/storage/raft/configuration or inspect network exposure of Vault API port (default 8200)
    Affected if Vault API port 8200 is accessible from untrusted networks

User is affected if running Vault Enterprise with an affected version AND using Integrated Storage AND the API is network-accessible to untrusted sources.

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 a release after 1.10.4
Interim mitigation

Upgrade Vault Enterprise to versions 1.9.8, 1.10.5, 1.11.1 or later. Until upgraded, restrict network access to Vault API endpoints to trusted networks only.

Recommended fix High confidence

Vault Enterprise 1.9.8, 1.10.5, or 1.11.1 depending on current branch (1.9.x, 1.10.x, or 1.11.x)

  1. Identify the current Vault Enterprise version by running 'vault version' on each node
  2. Determine the appropriate target version based on your current version (1.9.x -> 1.9.8, 1.10.x -> 1.10.5, 1.11.0 -> 1.11.1)
  3. Create a snapshot or backup of Vault data as a precaution before upgrading
  4. For each Vault node, stop the Vault service
  5. Upgrade Vault Enterprise to the appropriate fixed version (1.9.8, 1.10.5, or 1.11.1)
  6. Restart the Vault service on each node
  7. Verify the upgrade was successful by checking 'vault version' output
  8. Confirm the Integrated Storage cluster is healthy using 'vault operator raft list-peers'
Caveat Review HashiCorp Vault upgrade guides for version-specific considerations, though no breaking changes are noted in this CVE description

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

Fix this in Vault Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
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,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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