Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-5798: CWE-287: Improper Authentication in HashiCorp Vault

0
Low
VulnerabilityCVE-2024-5798cvecve-2024-5798cwe-287
Published: Wed Jun 12 2024 (06/12/2024, 18:55:24 UTC)
Source: CVE Database V5
Vendor/Project: HashiCorp
Product: Vault

Description

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

AI-Powered Analysis

AILast updated: 11/04/2025, 16:47:50 UTC

Technical Analysis

CVE-2024-5798 is a security vulnerability classified under CWE-287 (Improper Authentication) discovered in HashiCorp Vault and Vault Enterprise. The vulnerability stems from improper validation of the JSON Web Token (JWT) role-bound audience claim when using Vault's JWT authentication method. Specifically, Vault did not correctly verify that the JWT's audience claim matched the expected role-bound audience, allowing a JWT with mismatched claims to be accepted and an invalid login to succeed. This flaw undermines the authentication mechanism, potentially permitting attackers to authenticate with tokens that should have been rejected. The vulnerability affects Vault versions starting from 0.11.0 up to versions prior to 1.15.9, 1.16.3, and 1.17.0, where the issue was fixed. The CVSS v3.1 base score is 2.6, indicating low severity, with the vector indicating network attack vector, high attack complexity, required privileges, and user interaction, and a scope change with limited confidentiality impact. No known exploits have been reported in the wild as of the publication date (June 12, 2024). The vulnerability primarily impacts the authentication process, potentially allowing unauthorized access if exploited, but requires an attacker to have some level of privileges and user interaction, reducing the risk of widespread exploitation. The flaw is critical to address in environments relying on Vault for secrets management and authentication, especially where JWT-based authentication is in use.

Potential Impact

For European organizations, the improper authentication vulnerability in HashiCorp Vault could lead to unauthorized access to secrets and sensitive credentials managed by Vault if exploited. Although the CVSS score is low and exploitation requires privileges and user interaction, the impact on confidentiality could be significant in environments where Vault is a central component of the security infrastructure. Unauthorized logins could allow attackers to retrieve secrets, tokens, or credentials, potentially leading to lateral movement or data breaches. Organizations using vulnerable Vault versions in cloud-native, DevOps, or infrastructure automation contexts are at risk. The impact is heightened in sectors with strict compliance requirements such as finance, healthcare, and critical infrastructure, common in Europe. However, the limited ease of exploitation and absence of known active exploits reduce immediate risk. Nonetheless, failure to patch could expose organizations to targeted attacks, especially in high-value environments.

Mitigation Recommendations

European organizations should immediately upgrade HashiCorp Vault and Vault Enterprise to versions 1.15.9, 1.16.3, 1.17.0, or later to remediate CVE-2024-5798. Additionally, organizations should audit their JWT authentication configurations to ensure strict validation of audience and role-bound claims, preventing acceptance of tokens with mismatched claims. Implementing robust monitoring and alerting on authentication anomalies can help detect potential exploitation attempts. Restricting privileges to minimize who can authenticate via JWT and enforcing multi-factor authentication where possible will reduce risk. Regularly reviewing Vault audit logs for suspicious login activity is recommended. Organizations should also validate their incident response plans to quickly address any unauthorized access. Finally, educating DevOps and security teams about this vulnerability and secure JWT handling practices will strengthen overall security posture.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
HashiCorp
Date Reserved
2024-06-10T15:46:30.387Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 690a2ddcf0ba78a050535a85

Added to database: 11/4/2025, 4:46:20 PM

Last enriched: 11/4/2025, 4:47:50 PM

Last updated: 11/5/2025, 2:06:19 PM

Views: 1

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats