dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 7 Nov 2024. Known ransomware use
Veeam Backup \& ReplicationApplication · Veeam

CVE-2024-40711

CRITICAL · 9.8 CVSS v3.1 Published 2024-09-07
Fix available
A fix is available. Upgrade to 12.2.0.334 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit Remotely reachable No privileges 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 deserialization of untrusted data vulnerability with a malicious payload can allow an unauthenticated remote code execution (RCE).

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

This is a deserialization vulnerability where untrusted data is processed without proper validation, allowing attackers to inject malicious serialized payloads that execute arbitrary code on the target system remotely without requiring authentication.

MitigationApply vendor-provided security patches or upgrade to a patched version of the affected software; implement input validation and use safe deserialization libraries as compensating controls until patching is complete.

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.0.0.1420, < 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 Backup & Replication is installed
    Check the system for Veeam Backup & Replication installation by looking in Programs and Features (Windows) or using the package manager/repository for the operating system
    Affected if Veeam Backup & Replication is not installed on the system
  2. Identify the installed Veeam version
    Open Veeam Backup & Replication console and navigate to Help > About, or use the command line: run 'veeamversion' or check the Windows Registry under HKLM\SOFTWARE\Veeam\Veeam Backup & Replication
    Affected if The version cannot be determined or the product is not present
  3. Compare version against affected range
    Review the installed version number and compare it to the vulnerable range: versions 12.0.0.1420 or higher but lower than 12.2.0.334
    Affected if The installed version falls within >= 12.0.0.1420 and < 12.2.0.334
  4. Check for exposed deserialization interfaces
    Review Veeam service configuration and network exposure settings. Examine which Veeam services are listening on network ports and whether unauthenticated deserialization endpoints are accessible
    Affected if Untrusted deserialization input can be sent to Veeam services without authentication

A system is affected if Veeam Backup & Replication version is 12.0.0.1420 or higher but lower than 12.2.0.334, and the deserialization interface is accessible to untrusted input.

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-provided security patches or upgrade to a patched version of the affected software; implement input validation and use safe deserialization libraries as compensating controls until patching is complete.

Recommended fix High confidence

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

  1. Verify current Veeam Backup & Replication version by checking the About section in the Veeam console or using the command line: about -h
  2. Take a complete backup of the Veeam configuration using the Backup & Replication console or command line:veeamconfig backup create
  3. Review Veeam Upgrade Guide at docs.veeam.com for pre-upgrade requirements and compatibility checks
  4. Download Veeam Backup & Replication version 12.2.0.334 or later from portal.veeam.com
  5. Schedule maintenance window as upgrade will require service downtime
  6. Stop all Veeam services on the backup server before upgrade
  7. Run the Veeam Backup & Replication installer with upgrade option
  8. Follow installation wizard prompts to complete the upgrade
Caveat Review Veeam 12.2 release notes for potential configuration or feature changes; some backup job reconfiguration may be needed after upgrade

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

Fix this in Veeam Backup \& Replication Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get it fixed fast

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-40711 — 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-40711 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