CVE-2024-29855
Published: 11 June 2024
Summary
CVE-2024-29855 is a critical-severity Use of Hard-coded Credentials (CWE-798) vulnerability in Veeam Recovery Orchestrator. Its CVSS base score is 9.0 (Critical).
Operationally, ranked in the top 4.5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
CVE-2024-29855 is a hard-coded JWT secret vulnerability affecting Veeam Recovery Orchestrator. The issue is tracked under CWE-798 and received a CVSS v3 base score of 9.0, reflecting a network-accessible flaw with high attack complexity that can result in complete loss of confidentiality, integrity, and availability when exploited.
An unauthenticated attacker with network access can leverage the embedded secret to bypass authentication controls. This grants the ability to impersonate legitimate users or services and perform unauthorized actions within the orchestration environment, potentially leading to full system compromise.
Veeam addresses the issue in knowledge base article KB4585, which outlines mitigation steps and available patches for affected deployments.
The CVE maintains an EPSS score of 0.1912 with a recorded peak of 0.1946, indicating steady moderate exploitation interest since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-26847
Vulnerability details
Hard-coded JWT secret allows authentication bypass in Veeam Recovery Orchestrator
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Enables users to notice when hard-coded credentials have been exploited for unauthorized access.
Security training explicitly warns against hard-coded credentials, lowering their use in systems.
Policy and procedures prohibit hard-coded credentials in favor of managed authentication.
External identity providers eliminate the need for hard-coded credentials in applications.
Changing default authenticators prior to first use and protecting content prevents use of hard-coded credentials.
Central credential stores and rotation policies remove the need for hard-coded credentials in configuration files or code.
Intelligence programs surface reports of campaigns that abuse hard-coded credentials in products, prompting removal or replacement and thereby reducing successful exploitation.
Planned investment enables secure credential storage and management systems instead of hard-coded credentials.