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

Published Jul 11, 2024
·
Updated

Vault and Vault Enterprise did not properly handle requests originating from unauthorized IP addresses when the TCP listener option, proxyprotocolbehavior, was set to denyunauthorized. When receiving a request from a source IP address that was not listed in proxyprotocolauthorizedaddrs, 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 denyunauthorized 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

Affected Software

9 affected componentsFixes available
go/github.com/hashicorp/vault>=1.10.0<1.15.12
1.15.12
go/github.com/hashicorp/vault>=1.17.0-rc1<1.17.2
1.17.2
go/github.com/hashicorp/vault>=1.16.0-rc1<1.16.3
1.16.3
HashiCorp Vault>=1.10.0<1.15.12
HashiCorp Vault>=1.10.0<1.15.12
HashiCorp Vault>=1.16.0<1.16.6
HashiCorp Vault>=1.16.0<1.16.6
HashiCorp Vault>=1.17.0<1.17.2
HashiCorp Vault>=1.17.0<1.17.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/hashicorp/vault to a version that resolves this vulnerability.

    Fixed in 1.15.12
  2. Upgrade

    Upgrade go/github.com/hashicorp/vault to a version that resolves this vulnerability.

    Fixed in 1.17.2
  3. Upgrade

    Upgrade go/github.com/hashicorp/vault to a version that resolves this vulnerability.

    Fixed in 1.16.3
  4. Upgrade

    Upgrade Vault (and Vault Enterprise) to a version that resolves this vulnerability.

    Fixed in 1.17.2
  5. Upgrade

    Upgrade Vault (and Vault Enterprise) to a version that resolves this vulnerability.

    Fixed in 1.16.6
  6. Upgrade

    Upgrade Vault (and Vault Enterprise) to a version that resolves this vulnerability.

    Fixed in 1.15.12

Event History

Jul 11, 2024
CVE Published
via MITRE·08:40 PM
Data Sourced
via MITRE·08:40 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
Affected Software
Advisory Published
via GitHub·09:31 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-6468?

CVE-2024-6468 has been classified as a denial of service vulnerability.

2

How do I fix CVE-2024-6468?

To fix CVE-2024-6468, upgrade to Vault version 1.15.12, 1.16.3, or 1.17.2.

3

What software is affected by CVE-2024-6468?

CVE-2024-6468 affects HashiCorp Vault versions between 1.10.0 and 1.15.12, 1.16.0-rc1 and 1.16.3, and 1.17.0-rc1 and 1.17.2.

4

What is the impact of CVE-2024-6468?

The impact of CVE-2024-6468 is that unauthorized IP addresses can potentially disrupt service by not being properly handled.

5

What configurations are involved in CVE-2024-6468?

CVE-2024-6468 involves the configuration of the TCP listener option 'proxy_protocol_behavior' set to 'deny_unauthorized'.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203