# CVE-2024-2877: Vault Enterprise Leaks Sensitive HTTP Request Headers in the Audit Log When Deployed With a Performance Standby Node

> Attackers with audit log access can read sensitive HTTP headers from performance standby nodes in Vault Enterprise deployments.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 30 Apr 2024
- **Updated:** 13 Feb 2025
- **Also known as:** BIT-vault-2024-2877, GHSA-vxc5-78f8-rhp4

## What is CVE-2024-2877?

CVE-2024-2877 is a medium-severity vulnerability in Hashicorp Vault, published on 30 Apr 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Vault Enterprise, when configured with performance standby nodes and a configured audit device, will inadvertently log request headers on the standby node. These logs may have included sensitive HTTP request information in cleartext.

This vulnerability, CVE-2024-2877, was fixed in Vault Enterprise 1.15.8.

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

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

1 open source package ship an affected version, including vault. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vault` | Bitnami | From 1.15.0 | 1.15.8 |

Products: Hashicorp Vault.

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

Upgrade vault to 1.15.8 or later.

## Is CVE-2024-2877 being exploited?

There is no known exploitation of CVE-2024-2877 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-2877 and fix it if it is affected.

What it is: CVE-2024-2877 is a medium-severity vulnerability in Hashicorp Vault, published on 30 Apr 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-2877 in the wild and no public exploit code.

Affected packages and fixed versions:
- vault (Bitnami): affected from 1.15.0; fixed in 1.15.8

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-2877/ (Markdown: https://insights.sbomify.com/CVE-2024-2877/index.md)
```

## Sources

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

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