dbcve.org
Veeam Backup \& ReplicationApplication · Veeam

CVE-2024-40710

HIGH · 8.8 CVSS v3.1 Published 2024-09-07
Fix available
A fix is available. Upgrade to 12.2.0.334 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
A series of related high-severity vulnerabilities, the most notable enabling remote code execution (RCE) as the service account and extraction of sensitive information (savedcredentials and passwords). Exploiting these vulnerabilities requires a user who has been assigned a low-privileged role within Veeam Backup & Replication.

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 · moderate confidence

Multiple vulnerabilities in Veeam Backup & Replication allow a low-privileged authenticated user to achieve remote code execution as the service account and exfiltrate stored credentials and passwords. The chained exploitation leverages the existing user role permissions to escalate privileges and access sensitive credential storage.

MitigationApply vendor-supplied patches for CVE-2024-40710 immediately. Review and minimize user role assignments to the lowest privilege necessary while awaiting patch deployment.

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
Veeam Backup \& ReplicationApplication
Affected:< 12.2.0.334

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. Identify installed Veeam Backup & Replication version
    Access the Veeam Backup & Replication console or use the Veeam PowerShell toolkit (Get-VBRServerInfo or check Help > About in the GUI) to determine the exact build version installed
    Affected if The installed version is earlier than 12.2.0.334 (the fixed release)
  2. Review authenticated user accounts
    Open the Veeam Backup & Replication console, navigate to Users and Roles or use PowerShell (Get-VBRUser) to enumerate all configured users and service accounts with access to the installation
    Affected if Any low-privileged authenticated user account exists in the system (the vulnerability allows exploitation starting from minimal role permissions)
  3. Inspect stored credentials and password objects
    Check the Veeam credential manager (Credentials and Passwords section in the console) for any stored credentials for backup repositories, service accounts, or administrative accounts
    Affected if Stored credentials or passwords exist in the Veeam credential storage (these can be exfiltrated via the vulnerability)
  4. Verify service account configuration
    Review the service account used by Veeam Backup & Replication services (typically visible in Windows Services or via Veeam configuration database queries)
    Affected if The service runs under a high-privilege domain service account rather than a limited service account (this account would be compromised by successful RCE)

The environment is affected if Veeam Backup & Replication version is below 12.2.0.334 AND any authenticated user accounts with any role permissions exist in the system, particularly if stored credentials are present.

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 12.2.0.334 or later
Fixed in 12.2.0.334
Interim mitigation

Apply vendor-supplied patches for CVE-2024-40710 immediately. Review and minimize user role assignments to the lowest privilege necessary while awaiting patch deployment.

Recommended fix High confidence

Veeam Backup & Replication 12.2.0.334 or later (latest 12.2.x release)

  1. Ensure you have a complete backup of your Veeam Backup & Replication configuration and data
  2. Schedule a maintenance window for the upgrade process
  3. Download the latest Veeam Backup & Replication version 12.2.0.334 or later from the official Veeam website (www.veeam.com)
  4. Stop all Veeam services before beginning the upgrade
  5. Run the installer with administrator privileges
  6. Follow the on-screen installation wizard to complete the upgrade
  7. Verify that all Veeam services start successfully after upgrade
  8. Confirm the version number shows 12.2.0.334 or later in the Veeam console
Caveat Review Veeam release notes for any configuration or feature changes between your current version and 12.2.0.334

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

Fix this in Veeam Backup \& Replication Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-40710 — 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-40710 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