Vault Vulnerable to Denial of Service When Setting a Proxy Protocol Behavior
HashiCorp Vault · HashiCorp Vault Enterprise
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/hashicorp/vault Go |
|
|
HashiCorp Vault · HashiCorp Vault Enterprise
| Product | Affected | Fixed in |
|---|---|---|
| github.com/hashicorp/vault Go |
|
|
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.
From the CVE record · HashiCorp
Vault and Vault Enterprise can shut down their API server when an unauthorized source IP sends a request to a TCP listener configured with proxy_protocol_behavior set to deny_unauthorized. The server then stops responding to HTTP requests. The input notes that a separate regression prevented operators from configuring this option in the 1.16 and 1.17 release series through 1.16.5 and 1.17.1, respectively.
Operators of Vault or Vault Enterprise using the affected configuration should check their installations; the input lists affected Go package ranges beginning at 1.10.0, with the release-series qualification noted above.