CVE-2022-30689
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 · uneditedHashiCorp Vault and Vault Enterprise from 1.10.0 to 1.10.2 did not correctly configure and enforce MFA on login after server restarts. This affects the Login MFA feature introduced in Vault and Vault Enterprise 1.10.0 and does not affect the separate Enterprise MFA feature set. Fixed in 1.10.3.
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 confidenceVault 1.10.0-1.10.2 failed to correctly persist and enforce MFA (Multi-Factor Authentication) requirements for login after server restarts. The Login MFA feature introduced in 1.10.0 would not properly apply MFA policies following a restart, potentially allowing authenticated users to bypass MFA requirements until the next proper configuration reload.
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>= 1.10.0, < 1.10.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Vault versionRun 'vault version' command or check the Vault binary metadataAffected if The version is 1.10.0, 1.10.1, or 1.10.2 (>=1.10.0 and <1.10.3)
-
Determine if Login MFA is configuredRun 'vault auth list -detailed' and check for mfa_constraint entries, or query the sys/auth/mfa endpoint via APIAffected if Login MFA enforcement is configured on any auth method
-
Review authentication logs for time proximity to server restartsExamine Vault audit logs (stored in audit/ directory or sent to audit devices) for login events occurring shortly after 'Vault shutdown complete' or service restart messagesAffected if Logins occurred after a restart without triggering MFA prompts when MFA was expected to be enforced
-
Check for MFA validation failures or gaps in MFA audit logsQuery Vault audit logs for the 'mfa_response' field or look for login entries missing the expected MFA validation timestampAffected if Authenticated sessions exist without corresponding MFA validation records when MFA was configured
You are affected if Vault version is between 1.10.0 and 1.10.2 inclusive AND Login MFA is configured AND a server restart has occurred since configuration.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.10.3
Upgrade Vault and Vault Enterprise to version 1.10.3 or later to ensure MFA policies are correctly enforced after server restarts. In the interim, avoid restarting Vault servers or implement additional monitoring of authentication events.
Vault 1.10.3
- Back up your Vault data directory, configuration files, and encryption keys before upgrading
- Review the Vault 1.10.3 release notes at hashicorp.com for any behavior changes or migration requirements
- Download HashiCorp Vault version 1.10.3 from the official HashiCorp downloads page
- Stop the running Vault service gracefully
- Replace the Vault binary with version 1.10.3
- Review and update your Vault configuration files if required by the release notes
- Start the Vault service
- Verify the Vault cluster is healthy and operational
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30689 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-30689 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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