Vault Vulnerable to Denial of Service When Setting a Proxy Protocol Behavior
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.15.11, 1.15.12, 1.16.3, 1.17.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- 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/vaultGo
From 1.10.0 · fixed in 1.15.12
- github.com/hashicorp/vaultGo
From 1.16.0-rc1 · fixed in 1.16.3
- github.com/hashicorp/vaultGo
From 1.17.0-rc1 · fixed in 1.17.2
- github.com/hashicorp/vaultGo
From 1.10.0 · fixed in 1.16.3; From 1.17.0-rc1 · fixed in 1.17.2