CVE-2024-8365

Client-token disclosure via missing audit-log HMAC

Published Sep 2, 2024 · Updated Sep 4, 2024

Sensitive-data exposure in HashiCorp Vault 1.17.3 through 1.17.4 and Vault Enterprise 1.16.7 through 1.16.8 allows attackers to read client tokens. A regression removed HMAC processing for sensitive request headers, so configured audit devices wrote client tokens and token accessors as plaintext instead of keyed hashes. Exposure requires an enabled audit device, token-bearing API traffic, and access to its logs; disclosed tokens permit access within their assigned policies.

CVSS severity6.2
Medium
EPSS probability0.46%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Sensitive-data exposure in HashiCorp Vault 1.17.3 through 1.17.4 and Vault Enterprise 1.16.7 through 1.16.8 allows attackers to read client tokens. A regression removed HMAC processing for sensitive request headers, so configured audit devices wrote client tokens and token accessors as plaintext instead of keyed hashes. Exposure requires an enabled audit device, token-bearing API traffic, and access to its logs; disclosed tokens permit access within their assigned policies.

The record

CVE
CVE-2024-8365
Published
Sep 2, 2024
Updated
Sep 4, 2024
Vendor
HashiCorp
Product
Vault
Classifications
CWE-532, T1552.001
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Sep 2, 2024CVE publishedPublication date reported by the CVE source.
  2. Sep 4, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=1.17.3 <1.17.5

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

HashiCorp · Vaultversion=1.17.3 <1.17.5
HashiCorp · Vault Enterpriseversion=1.16.7 <1.17.5 changes=[{"at":"1.16.9","status":"unaffected"},{"at":"1.17.3","status":"unaffected"}]

Published CVSS scores

6.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
6.2HashiCorp Inc.CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-532Insertion of Sensitive Information into Log File
T1552.001Credentials In Files

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo