dbcve.org
VaultApplication · Hashicorp

CVE-2024-6468

HIGH · 7.5 CVSS v3.1 Published 2024-07-11
Fix available
A fix is available. Upgrade to 1.15.12 / 1.16.6 or later.
See remediation →
84/100
Remediation priority · High
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
Vault and Vault Enterprise did not properly handle requests originating from unauthorized IP addresses when the TCP listener option, proxy_protocol_behavior, was set to deny_unauthorized. When receiving a request from a source IP address that was not listed in proxy_protocol_authorized_addrs, the Vault API server would shut down and no longer respond to any HTTP requests, potentially resulting in denial of service. While this bug also affected versions of Vault up to 1.17.1 and 1.16.5, a separate regression in those release series did not allow Vault operators to configure the deny_unauthorized option, thus not allowing the conditions for the denial of service to occur. Fixed in Vault and Vault Enterprise 1.17.2, 1.16.6, and 1.15.12.

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 and Vault Enterprise failed to properly handle requests from unauthorized IP addresses when proxy_protocol_behavior was set to deny_unauthorized. Requests from IPs not in proxy_protocol_authorized_addrs caused the Vault API server to shut down and stop responding, resulting in denial of service.

MitigationUpgrade to Vault 1.17.2, 1.16.6, or 1.15.12 or later to receive the patch. Alternatively, avoid using the deny_unauthorized setting for proxy_protocol_behavior until the upgrade is completed.

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.10.0, < 1.15.12>= 1.16.0, < 1.16.6>= 1.17.0, < 1.17.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Check Vault version
    Run `vault version` to determine the installed version
    Affected if Version is >= 1.10.0 and < 1.15.12, OR >= 1.16.0 and < 1.16.6, OR >= 1.17.0 and < 1.17.2
  2. Locate Vault configuration file
    Find the Vault server configuration file (typically at /etc/vault/config.hcl or /etc/vault.d/vault.hcl)
    Affected if Configuration file exists and is in use by the Vault instance
  3. Check proxy_protocol_behavior setting
    Inspect the configuration file for the `proxy_protocol_behavior` setting
    Affected if The setting is present and set to "deny_unauthorized"
  4. Verify proxy_protocol_authorized_addrs configuration
    Check if `proxy_protocol_authorized_addrs` is configured in the same file
    Affected if The deny_unauthorized behavior is active with any authorized addresses configured (requests from non-listed IPs will trigger the DoS)

A user is affected if they run a vulnerable Vault version with proxy_protocol_behavior set to deny_unauthorized in their configuration.

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.15.12 / 1.16.6 / 1.17.2 or later
Fixed in 1.15.121.16.61.17.2
Interim mitigation

Upgrade to Vault 1.17.2, 1.16.6, or 1.15.12 or later to receive the patch. Alternatively, avoid using the deny_unauthorized setting for proxy_protocol_behavior until the upgrade is completed.

Recommended fix High confidence

Vault 1.17.2 (or 1.16.6 or 1.15.12 depending on your version branch)

  1. 1. Take a complete backup of Vault data and configuration, including the snapshot of the storage backend
  2. 2. Test the upgrade in a non-production environment first
  3. 3. Upgrade Vault to one of the fixed versions: 1.17.2, 1.16.6, or 1.15.12 depending on your current version branch
  4. 4. After upgrading, verify the proxy_protocol_behavior setting is properly configured in your listener configuration
  5. 5. Test that Vault is responding correctly to requests
  6. 6. Monitor Vault logs for any errors or issues
  7. 7. Once validated in non-production, schedule maintenance window and upgrade production systems
Caveat Review HashiCorp Vault upgrade notes for your target version as there may be behavior changes between major versions; always test upgrades in non-production first

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

Fix this in Vault Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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