CVE-2024-29855

9.0 CRITICAL

📋 TL;DR

CVE-2024-29855 is a critical authentication bypass vulnerability in Veeam Recovery Orchestrator caused by a hard-coded JWT secret. Attackers can forge valid authentication tokens to gain unauthorized access to the system. All organizations using affected versions of Veeam Recovery Orchestrator are vulnerable.

💻 Affected Systems

Products:
  • Veeam Recovery Orchestrator
Versions: All versions prior to the fixed version
Operating Systems: Windows
Default Config Vulnerable: ⚠️ Yes
Notes: All deployments of affected versions are vulnerable regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of the Veeam Recovery Orchestrator environment, allowing attackers to access, modify, or delete backup and recovery configurations, potentially disrupting disaster recovery capabilities.

🟠

Likely Case

Unauthorized access to sensitive backup configurations, recovery plans, and potentially access to backup repositories, leading to data exposure or manipulation.

🟢

If Mitigated

Limited impact if system is isolated behind strong network controls and access is restricted, though authentication bypass remains possible.

🌐 Internet-Facing: HIGH - If exposed to the internet, attackers can easily exploit this without authentication to gain full system access.
🏢 Internal Only: HIGH - Even internally, any user with network access to the system can exploit this vulnerability to bypass authentication.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires knowledge of the hard-coded secret, which may be discovered through reverse engineering or information disclosure.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check Veeam KB4585 for specific fixed version

Vendor Advisory: https://www.veeam.com/kb4585

Restart Required: Yes

Instructions:

1. Download the latest patch from Veeam's official website. 2. Apply the patch following Veeam's installation instructions. 3. Restart the Veeam Recovery Orchestrator service. 4. Verify the fix by checking the version.

🔧 Temporary Workarounds

Network Isolation

all

Restrict network access to Veeam Recovery Orchestrator to only trusted administrative networks

Access Control Lists

all

Implement strict firewall rules and network segmentation to limit who can reach the Veeam Recovery Orchestrator interface

🧯 If You Can't Patch

  • Immediately isolate the Veeam Recovery Orchestrator system from all untrusted networks
  • Implement additional authentication layers such as VPN or bastion host requirements for access

🔍 How to Verify

Check if Vulnerable:

Check your Veeam Recovery Orchestrator version against the affected versions listed in Veeam KB4585

Check Version:

Check the Veeam Recovery Orchestrator console or administration interface for version information

Verify Fix Applied:

Verify the version has been updated to the patched version specified in Veeam KB4585

📡 Detection & Monitoring

Log Indicators:

  • Unusual authentication patterns
  • Access from unexpected IP addresses
  • Failed login attempts followed by successful JWT token usage

Network Indicators:

  • Unusual API calls to authentication endpoints
  • Traffic patterns indicating token forging attempts

SIEM Query:

source="veeam-recovery-orchestrator" AND (event_type="authentication" AND result="success") AND src_ip NOT IN [trusted_ip_list]

🔗 References

📤 Share & Export