CVE-2024-6468 | Vault Vulnerable to Denial of Service When Setting a Proxy Protocol Behavior

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.

Published: 2024-07-11 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-6468 is rated Moderate Risk (43.4/100): CVSS High severity, with low exploitation likelihood (EPSS 0.49%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-6468

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.40% 0.49% +0.10%
2 2025-12-28 0.34% 0.40% +0.05%
3 2025-12-27 — 0.34% —

Full EPSS history (15 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-6468

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2024-6468

GitHub Security Advisory for CVE-2024-6468

GHSA-2qmw-pvf7-4mw6 · Severity: high · Ecosystem: go — Hashicorp Vault vulnerable to Improper Check or Handling of Exceptional Conditions

OS Trackers for CVE-2024-6468

vendor priority summary link
alpine — CVE-2024-6468: 1 source package rows (vault); 3 state rows across 1 repos (edge-community); fixed 0, open 3. https://security.alpinelinux.org/vuln/CVE-2024-6468
redhat high — https://access.redhat.com/security/cve/CVE-2024-6468

Affected software / configurations for CVE-2024-6468

Vendor Product Version Raw CPE
hashicorp vault >= 1.10.0, < 1.15.12 cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:*
hashicorp vault >= 1.10.0, < 1.15.12 cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*
hashicorp vault >= 1.16.0, < 1.16.6 cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:*
hashicorp vault >= 1.16.0, < 1.16.6 cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*
hashicorp vault >= 1.17.0, < 1.17.2 cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:*
hashicorp vault >= 1.17.0, < 1.17.2 cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*

References for CVE-2024-6468

cvelogic Threat Intelligence