CVE-2024-2877
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVault 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceVault Enterprise with performance standby nodes and a configured audit device inadvertently logs HTTP request headers in cleartext on standby nodes, potentially exposing sensitive authentication credentials, cookies, or other header-based secrets through audit logs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.15.0, < 1.15.8CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Vault Enterprise is in useRun 'vault version' and check the build information. Enterprise builds include 'ent' or 'enterprise' in the version string. Open-source Vault is not affected by this vulnerability.Affected if Running Vault Enterprise (not open-source Vault)
-
Determine the installed Vault versionExecute 'vault version' to obtain the exact version number. Compare against the affected range: 1.15.0 through 1.15.7 inclusive.Affected if Installed version is >= 1.15.0 and < 1.15.8
-
Verify performance standby nodes are configuredCheck Vault configuration files (usually in /etc/vault.d/) for 'cluster_addr' and 'disable_clustering' settings, or run 'vault operator raft list-peers' to enumerate cluster members. Performance standbys appear as 'non-voter' or 'standby' nodes in raft configuration.Affected if Performance standby nodes are present in the Vault cluster
-
Confirm an audit device is enabledRun 'vault audit list -detailed' to list all configured audit devices. At least one audit device (file, syslog, socket, etc.) must be enabled for this vulnerability to expose data.Affected if One or more audit devices are enabled and operational
-
Inspect audit logs for cleartext HTTP headersExamine audit log files (typically in /var/log/vault/ or configured audit sink paths) for entries containing request headers. Look for log entries with 'request_headers' fields that may contain authentication tokens, cookies, or other sensitive header values in plaintext.Affected if Audit logs contain plaintext HTTP headers from requests handled by standby nodes
You are affected if running Vault Enterprise with performance standby nodes, at least one audit device configured, and version 1.15.0 through 1.15.7 inclusive.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.15.8
Upgrade to Vault Enterprise 1.15.8 or later. Review existing audit logs for any unauthorized access and rotate potentially exposed credentials.
Vault Enterprise 1.15.8 or later
- Upgrade Vault Enterprise from any version >= 1.15.0 and < 1.15.8 to version 1.15.8 or later
- After upgrading, verify that audit logs on performance standby nodes no longer contain sensitive HTTP request headers in cleartext
- Review existing audit logs for any potential exposure of sensitive HTTP request information that may have occurred prior to the patch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2877 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-2877 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data