CVE-2024-2660
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 · uneditedVault and Vault Enterprise TLS certificates auth method did not correctly validate OCSP responses when one or more OCSP sources were configured. This vulnerability, CVE-2024-2660, affects Vault and Vault Enterprise 1.14.0 and above, and is fixed in Vault 1.16.0 and Vault Enterprise 1.16.1, 1.15.7, and 1.14.11.
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 confidenceThe TLS certificates authentication method in Vault and Vault Enterprise failed to properly validate OCSP (Online Certificate Status Protocol) responses when one or more OCSP sources were configured, potentially allowing revoked certificates to be accepted for authentication.
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.14.0, < 1.14.11>= 1.14.0, < 1.16.0>= 1.15.0, < 1.15.7CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Vault versionRun `vault version` or check the Vault server log at startup for the version numberAffected if Version is 1.14.0 through 1.14.10, 1.15.0 through 1.15.6, or 1.14.11 through 1.15.x (before 1.16.0)
-
Verify TLS certificates auth method is enabledRun `vault auth list` to see enabled auth methods, or query the sys/auth endpointAffected if A method of type "cert" is listed as enabled
-
Check if OCSP is configured as a certificate validation sourceExamine the TLS cert auth method configuration using `vault read auth/cert` or inspect the configuration file for ocsp_server_ns fields or ocsp addressesAffected if OCSP servers are configured in the cert auth method configuration (ocsp_server_ns or ocsp_query_server settings are present)
-
Confirm OCSP response validation is in useReview the cert auth method config for `ocsp_enabled` set to true, or check if ocsp_fail_open or ocsp_query_all_urls options are presentAffected if OCSP validation is actively enabled for certificate status checks
User is affected if Vault version is in the vulnerable range AND TLS certs auth method is enabled with OCSP sources configured for certificate validation.
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.14.111.15.71.16.0
Upgrade Vault to version 1.16.0 or later (or Vault Enterprise 1.16.1, 1.15.7, 1.14.11 or later) to remediate this OCSP validation bypass in the TLS certs auth method.
Vault 1.14.11 (for 1.14.x), Vault 1.15.7 (for 1.15.x), or Vault 1.16.0+ (for latest stable)
- 1. Identify the current Vault version by running `vault version`
- 2. Determine the appropriate upgrade path based on current version (1.14.x -> 1.14.11, 1.15.x -> 1.15.7, or to 1.16.x)
- 3. Review the Vault upgrade guide at https://developer.hashicorp.com/vault/docs/upgrading
- 4. Take a backup of Vault data using `vault operator raft snapshot save` or appropriate storage snapshot
- 5. Test the upgrade in a non-production environment first
- 6. Stop the Vault service
- 7. Install the new Vault binary (1.14.11, 1.15.7, or 1.16.0+)
- 8. Start the Vault service and verify it runs successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2660 — 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-2024-2660 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