Skip to content
Fencer Vulns
medium 6.2

CVE-2024-8365 json

Vault Leaks AppRole Client Tokens And Accessor in Audit Log

published 2024-09-02 2 y ago modified 2026-09-10 1 mo ago also BIT-vault-2024-8365 , EUVD-2024-2824 , GHSA-jjxf-26c9-77gm , GO-2024-3113

cvss
6.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 39%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/hashicorp/vault 1.17.5
  • bitnami vault 1.16.9, 1.17.5
  • HashiCorp Vault 1.17.5
  • HashiCorp Vault Enterprise 1.16.9, 1.17.3, 1.17.5

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-8365 updated cvss 6.2

vault: Vault Leaks Client Token and Token Accessor in Audit Devices

  • Red Hat Openshift Container Storage 4 ocs4/cephcsi-rhel8, ocs4/mcg-rhel8-operator, ocs4/ocs-rhel8-operator, ocs4/ocs-must-gather-rhel8, ocs4/rook-ceph-rhel8-operator Red Hat Openshift Data Foundation 4 odf4/cephcsi-rhel9, odf4/mcg-cli-rhel9, odf4/odf-cli-rhel9, odf4/mcg-rhel9-operator, odf4/ocs-rhel9-operator, odf4/odf-rhel8-operator, +4 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.46% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/hashicorp/vault
>=1.17.3, <1.17.5
1.17.5
bitnami vault
>=1.16.7, <1.16.9
>=1.17.3, <1.17.5
1.16.9
1.17.5

Affected products

  • HashiCorp Vault
  • HashiCorp Vault Enterprise

Classification

Weakness
  • CWE-532 Insertion of Sensitive Information into Log File

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.