CVE-2024-6468 Affecting vault-fips-1.17 package, versions <1.17.2-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.04% (11th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-VAULTFIPS117-7448324
  • published13 Jul 2024
  • disclosed11 Jul 2024

Introduced: 11 Jul 2024

CVE-2024-6468  (opens in a new tab)

How to fix?

Upgrade Chainguard vault-fips-1.17 to version 1.17.2-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream vault-fips-1.17 package and not the vault-fips-1.17 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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.