dbcve.org
Recovery OrchestratorApplication · Veeam

CVE-2024-22022

HIGH · 8.8 CVSS v3.1 Published 2024-02-07
Fix available
A fix is available. Upgrade to 7.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability CVE-2024-22022 allows 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Veeam Recovery Orchestrator contains a vulnerability where users assigned low-privileged roles can access the NTLM hash of the service account used by the Veeam Orchestrator Server Service. This credential disclosure enables potential pass-the-hash attacks or offline hash cracking to recover plaintext credentials.

MitigationApply vendor-provided patches for CVE-2024-22022. Until patched, restrict low-privileged user access to sensitive resources and monitor for anomalous authentication behavior using the compromised service account hash.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Recovery OrchestratorApplication
Affected:< 7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Veeam Recovery Orchestrator is installed
    Check for Veeam Recovery Orchestrator in installed programs via Windows Control Panel > Programs and Features, or run: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName | Where-Object {$_.DisplayName -like '*Veeam Recovery Orchestrator*'}
    Affected if Veeam Recovery Orchestrator appears in the installed programs list
  2. Determine installed version of Veeam Recovery Orchestrator
    Run: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion | Where-Object {$_.DisplayName -like '*Veeam Recovery Orchestrator*'} OR check the About section in the VRO administration console
    Affected if The displayed version number is lower than 7.0 (for example 6.x, 5.x, etc.)
  3. Confirm service account configuration exists
    In Veeam Recovery Orchestrator administration console, navigate to Settings > Service Account or check Windows Services for 'Veeam Orchestrator Server Service' and view the service account configured under the Log On tab
    Affected if The service is running under a specific service account (not LocalSystem) and VRO version is below 7.0
  4. Verify low-privileged role assignments
    In VRO administration console, navigate to Users and Roles to review which users are assigned to low-privileged roles such as Read-Only User, Restore Operator, or custom roles with limited permissions
    Affected if Any low-privileged user accounts exist in the system and VRO version is below 7.0

A user is affected if Veeam Recovery Orchestrator version is below 7.0 and low-privileged users have access to the system where the NTLM hash could be retrieved.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.0 or later
Fixed in 7.0
Interim mitigation

Apply vendor-provided patches for CVE-2024-22022. Until patched, restrict low-privileged user access to sensitive resources and monitor for anomalous authentication behavior using the compromised service account hash.

Recommended fix Moderate confidence

Veeam Recovery Orchestrator 7.0 or later

  1. 1. Review the current Veeam Recovery Orchestrator version by navigating to the Administration panel or checking the installed software.
  2. 2. Plan for upgrade during a maintenance window, ensuring proper backups of configuration data.
  3. 3. Download Veeam Recovery Orchestrator version 7.0 or later from the official Veeam download portal (https://www.veeam.com/downloads.html).
  4. 4. Execute the installer with administrative privileges, following the upgrade wizard prompts.
  5. 5. Verify the upgrade was successful by checking the version number in the Administration panel.
  6. 6. Confirm the vulnerability is remediated by verifying that low-privileged users can no longer access NTLM hashes through the affected interface.
Caveat Review Veeam release notes for version 7.0 to check for any configuration or workflow changes that may affect existing setups

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Recovery Orchestrator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22022 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-22022 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data