#1 Global Leader in Data Resilience
#1 Global Leader in Data Resilience
BACK TO KB LIST

Veeam Recovery Orchestrator Vulnerability (CVE-2024-29855)

KB ID: 4585
Product: Veeam Recovery Orchestrator | 7.0 | 7.1
Published: 2024-06-10
Last Modified: 2024-09-23
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Veeam Software Security Commitment
Veeam® is committed to ensuring its products protect customers from potential risks. As part of that commitment, we operate a Vulnerability Disclosure Program (VDP) for all Veeam products and perform extensive internal code audits. When a vulnerability is identified, our team promptly develops a patch to address and mitigate the risk. In line with our dedication to transparency, we publicly disclose the vulnerability and provide detailed mitigation information. This approach ensures that all potentially affected customers can quickly implement the necessary measures to safeguard their systems. It’s important to note that once a vulnerability and its associated patch are disclosed, attackers will likely attempt to reverse-engineer the patch to exploit unpatched deployments of Veeam software. This reality underscores the critical importance of ensuring that all customers use the latest versions of our software and install all updates and patches without delay.
Article Applicability

This article documents a vulnerability discovered in the Web Console component of Veeam Recovery Orchestrator.

This vulnerability does not affect other Veeam products (e.g., Veeam Backup & Replication, Veeam Agent for Microsoft Windows, Veeam ONE, Veeam Service Provider Console, etc.).

Issue Details

CVE-2024-29855

A vulnerability (CVE-2024-29855) in Veeam Recovery Orchestrator (VRO) version 7.0.0.337 allows an attacker to access the VRO web UI with administrative privileges.

Note: The attacker must know the exact username and role of an account that has an active VRO UI access token to accomplish the hijack.

Severity: Critical
CVSS 3.1 Score: 9.0CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Solution

The vulnerability discussed in this article was resolved starting in:

  • Veeam Recovery Orchestrator 7.1.0.230
  • Veeam Recovery Orchestrator 7.0.0.379

Deployment Information

New Veeam Recovery Orchestrator Release

All customers are advised to upgrade their Veeam Recovery Orchestrator deployment to version 7.1.0.278 or higher.

Note: Veeam Recovery Orchestrator 7.1.0.278 is included within VeeamDataPlatform_23H2_20240825.iso.

The patches below only resolve the vulnerability documented in this article for Veeam Recovery Orchestrator. They do not mitigate the announced vulnerabilities that exist in the build of Veeam Backup & Replication used by Veeam Recovery Orchestrator 7.0.0.337 or 7.1.0.205. For that reason, we strongly encourage all customers to upgrade to Veeam Recovery Orchestrator version 7.1.0.278 or higher, which utilizes the latest Veeam Backup & Replication and Veeam ONE releases to mitigate the vulnerabilities announced in KB4649.

The updated build number will only be displayed within the Programs & Features (appwiz.cpl) entry for Veeam Recovery Orchestrator. The build number shown within the UI and logs will still be listed as the previous version.

The build number displayed in the UI and logs will be updated in the next Veeam Recovery Orchestrator release.

For Veeam Recovery Orchestrator build 7.0.0.337

For environments operating VRO 7.0.0.337, either upgrade to 7.1.0.230 or install the following patch to update to build 7.0.0.379.

To update: download the patch (.msp) file and execute it on the VRO server using an Administrative Command Prompt or Administrative PowerShell console.

Download VRO 7.0.0.337 to 7.0.0.379 Patch
Filename:  VRO.WebUI.x64_7.0.0.379.msp
MD5: B7997EEDC6BFF93C78B40D6F416245AE
SHA1: C9BDA93F41E9D83B9D17A2570840FE1EB5F5C5E6
 

For Veeam Recovery Orchestrator build 7.1.0.205

For environments operating VRO 7.1.0.205, install the following patch to update to build 7.1.0.230.

To update: download the patch (.msp) file and execute it on the VRO server using an Administrative Command Prompt or Administrative PowerShell console.

Download VRO 7.1.0.205 to 7.1.0.230 Patch
Filename: VRO.WebUI.x64_7.1.0.230.msp
MD5: 357E4D897ABECA9955A90CE2A5B38611
SHA1: 5703D14AE437FB0BDD47FB44EB278CFBDD80C0CE

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Start using Veeam:
Download the product
&
Activate the license key
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.