CVE-2024-8365: Vault Community Edition and Vault Enterprise experienced a regression where functionality that HMAC’d sensitive headers in the configured audit device, specifically client tokens and token...
Medium CVSS 6.5
- CVE id
- CVE-2024-8365
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| HashiCorp Vault Runtimes and servers |
< 1.17.5 | 1.17.5 |
| HashiCorp Vault Enterprise Runtimes and servers |
< 1.16.9 < 1.17.5 >= 1.17.0, < 1.17.5 |
1.16.9, 1.17.5 |
How to fix it
HashiCorp Vault (Runtimes and servers)
Upgrade HashiCorp Vault to 1.17.5 or later.
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.16.9, 1.17.5.
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 Community Edition and Vault Enterprise experienced a regression where functionality that HMAC’d sensitive headers in the configured audit device, specifically client tokens and token accessors, was removed. This resulted in the plaintext values of client tokens and token accessors being stored in the audit log. This vulnerability, CVE-2024-8365, was fixed in Vault Community Edition and Vault Enterprise 1.17.5 and Vault Enterprise 1.16.9.
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.
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.