CVE-2024-5798GHSA-32CJ-5WX4-GQ8PBIT-VAULT-2024-5798GO-2024-2921
Vault Incorrectly Validated JSON Web Tokens (JWT) Audience Claims
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.14.13, 1.17.0, 1.16.3, 1.15.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Vault and Vault Enterprise did not properly validate the JSON Web Token (JWT) role-bound audience claim when using the Vault JWT auth method. This may have resulted in Vault validating a JWT the audience and role-bound claims do not match, allowing an invalid login to succeed when it should have been rejected. This vulnerability, CVE-2024-5798, was fixed in Vault and Vault Enterprise 1.17.0, 1.16.3, and 1.15.9
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- HashiCorp Vault
From 0.11.0 · fixed in 1.14.13
- HashiCorp Vault Enterprise
From 0.11.0 · fixed in 1.14.13
- github.com/hashicorp/vaultGo
From 1.17.0-rc1 · fixed in 1.17.0
- github.com/hashicorp/vaultGo
From 1.16.0-rc1 · fixed in 1.16.3
- github.com/hashicorp/vaultGo
From 0.11.0 · fixed in 1.15.9
- github.com/hashicorp/vaultGo
From 0.11.0 · fixed in 1.16.3; From 1.17.0-rc1 · fixed in 1.17.0