CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
AI Score
Confidence
High
EPSS
Percentile
19.3%
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
The issues documented in this article affect the following versions:
Veeam Recovery Orchestrator 7 is not impacted by these issues.
Vulnerability CVE-2024-22021allows a Veeam Recovery Orchestrator user with a low privileged role (Plan Author) to retrieve plans from a Scope other than the one they are assigned to.
Affected Version(s)*:
Severity: Medium CVSS v3.1 Score: 4.5
Vulnerability CVE-2024-22022allows a Veeam Recovery Orchestrator user that has been assigned a low-privileged role to access the NTLM hash of the service account used by the Veeam Orchestrator Server Service.
Affected Version(s)*:
Severity: High CVSS v3.1 Score: 8.8
*Vulnerability testing was only performed using actively supported versions of Veeam Recovery Orchestrator.
The vulnerabilities documented in this article are already fixed in Veeam Recovery Orchestrator version 7.
Customers are advised to upgrade to the latest Veeam Recovery Orchestrator version.
Veeam strongly recommends that customers use the most recent version of the software. However, we understand some environments may require additional planning and time to deploy an upgrade. In recognition of this, a patch has been developed for Veeam Recovery Orchestrator 6 that resolves the vulnerabilities discussed in this article. We encourage affected users who are unable to upgrade to Veeam Recovery Orchestrator 7 to apply this patch as soon as possible to maintain system security.
Requirements
This patch requires Veeam Recovery Orchestrator 6 P20230419 (6.0.0.3516).
To check which version is installed, switch to Administration view, then select the About section.
Preparation
Update Procedure
On the Veeam Recovery Orchestrator server, run VDRO.Server.x64_6.0.0.3582.msp.
On the server where the Veeam Recovery Orchestrator web UI is installed, run VDRO.WebUI.x64_6.0.0.3582.msp.
Reboot may be required
Please note that a reboot may be required after installing the patch.
Please plan accordingly.
The patch below was built for Veeam Recovery Orchestrator 6 P20230419 (6.0.0.3516).
Filename: KB4541.VDRO.x64_6.0.0.3582.zip
MD5: B4B6939B548E69652FF36C33D2B6779A
SHA1: E084B1D158AD1297B42B26B149D71184AAE6D0B5
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.
Vendor | Product | Version | CPE |
---|---|---|---|
veeam | recovery_orchestrator | 6.0 | cpe:2.3:a:veeam:recovery_orchestrator:6.0:*:*:*:*:*:*:* |
veeam | recovery_orchestrator | 5.0 | cpe:2.3:a:veeam:recovery_orchestrator:5.0:*:*:*:*:*:*:* |
veeam | recovery_orchestrator | 4.0 | cpe:2.3:a:veeam:recovery_orchestrator:4.0:*:*:*:*:*:*:* |