CVE-2024-6468: 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.

High CVSS 7.5

CVE id
CVE-2024-6468
Published
Last modified

Affected packages

PackageAffected versionsFixed in
HashiCorp Vault
Runtimes and servers
>= 1.10.0, < 1.15.12
>= 1.16.0, < 1.16.6
>= 1.17.0, < 1.17.2
1.15.12, 1.16.6, 1.17.2
HashiCorp Vault Enterprise
Runtimes and servers
>= 1.10.0, < 1.15.12
>= 1.16.0, < 1.16.6
>= 1.17.0, < 1.17.2
1.15.12, 1.16.6, 1.17.2

How to fix it

HashiCorp Vault (Runtimes and servers)

Upgrade HashiCorp Vault to the fixed release of the line you run: 1.15.12, 1.16.6, 1.17.2.

vault version
  • Upgrade Vault (the hashicorp/vault image or binary) to the patched release.

HashiCorp Vault Enterprise (Runtimes and servers)

Upgrade HashiCorp Vault Enterprise to the fixed release of the line you run: 1.15.12, 1.16.6, 1.17.2.

vault version
  • Upgrade Vault Enterprise (the hashicorp/vault-enterprise image or binary) to the patched release.

A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.

Details

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 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.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.