# CVE-2024-8365: Vault Leaks AppRole Client Tokens And Accessor in Audit Log

> Attackers with audit log access can read plaintext client tokens and accessors due to missing HMAC masking, potentially leading to unauthorized access.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Sep 2024
- **Updated:** 4 Sep 2024
- **Also known as:** BIT-vault-2024-8365, GHSA-jjxf-26c9-77gm, GO-2024-3113

## What is CVE-2024-8365?

CVE-2024-8365 is a medium-severity vulnerability in Hashicorp Vault, published on 2 Sep 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2024-8365?

4 open source packages ship an affected version, including github.com/hashicorp/vault and vault. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/hashicorp/vault` | Go | From 1.17.3 | 1.17.5 |
| `github.com/hashicorp/vault` | Go | From 1.17.3 | 1.17.5 |
| `github.com/hashicorp/vault` | Go | From 1.17.3 | 1.17.5 |
| `vault` | Bitnami | From 1.16.7 | 1.16.9, 1.17.5 |

Products: Hashicorp Vault.

## How do I fix CVE-2024-8365?

Upgrade github.com/hashicorp/vault to 1.17.5 or later.

## Is CVE-2024-8365 being exploited?

There is no known exploitation of CVE-2024-8365 in the wild and no public exploit code.

## Other vulnerabilities in Hashicorp Vault

- [CVE-2020-35192](https://insights.sbomify.com/CVE-2020-35192/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-12757](https://insights.sbomify.com/CVE-2020-12757/): Improper Input Validation in HashiCorp Vault (critical 9.8)
- [CVE-2025-6000](https://insights.sbomify.com/CVE-2025-6000/): Arbitrary Remote Code Execution via Plugin Catalog Abuse (critical 9.1)
- [CVE-2022-40186](https://insights.sbomify.com/CVE-2022-40186/): HashiCorp Vault vulnerable to incorrect metadata access (critical 9.1)
- [CVE-2022-36129](https://insights.sbomify.com/CVE-2022-36129/): Missing authorization in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8365 and fix it if it is affected.

What it is: CVE-2024-8365 is a medium-severity vulnerability in Hashicorp Vault, published on 2 Sep 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-8365 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/hashicorp/vault (Go): affected from 1.17.3; fixed in 1.17.5
- github.com/hashicorp/vault (Go): affected from 1.17.3; fixed in 1.17.5
- github.com/hashicorp/vault (Go): affected from 1.17.3; fixed in 1.17.5
- vault (Bitnami): affected from 1.16.7; fixed in 1.16.9, 1.17.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-8365/ (Markdown: https://insights.sbomify.com/CVE-2024-8365/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-8365
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-8365
- OSV: https://osv.dev/vulnerability/CVE-2024-8365

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-8365/
Summaries are generated and may contain mistakes; the official description above is the record.