dbcve.org
Veeam Backup \& ReplicationApplication · Veeam

CVE-2024-39718

HIGH · 8.1 CVSS v3.1 Published 2024-09-07
Fix available
A fix is available. Upgrade to 12.2.0.334 or later.
See remediation →
87/100
Remediation priority · High
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
An improper input validation vulnerability that allows a low-privileged user to remotely remove files on the system with permissions equivalent to those of the service account.

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 an input validation vulnerability where the application fails to properly validate file path inputs before processing file deletion requests. A low-privileged authenticated user can exploit this to delete arbitrary files on the system, with the operations executing under the elevated permissions of the service account rather than the restricted user context.

MitigationImplement strict input validation and authorization checks on all file operations, ensuring low-privileged users can only delete files within their designated directories and cannot manipulate path traversal sequences or special characters to access protected filesystem locations.

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.1402, < 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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 Veeam Backup & Replication installation
    Locate the Veeam installation directory or check installed programs. Common paths: C:\Program Files\Veeam\Backup and Replication\ or review installed software via Windows Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
    Affected if Veeam Backup & Replication is installed on the system
  2. Determine installed version
    Check the version of Veeam Backup & Replication. The version can typically be found in the product UI under Help > About, or by reviewing the installation log or registry entries under the Veeam installation directory
    Affected if Installed version is >= 12.0.0.1402 and < 12.2.0.334
  3. Verify authentication mechanism is enabled
    Confirm that the Veeam Backup & Replication web console or API service is accessible and user authentication is enabled. This service typically runs on ports 9419 or 9443
    Affected if Web console or API is accessible with user authentication configured
  4. Check for low-privileged user accounts
    Review configured users and roles in Veeam Backup & Replication. Low-privilege accounts with any file operation permissions (even limited) could potentially exploit this path traversal during file deletion operations
    Affected if Low-privileged authenticated users exist with any file deletion permissions or API access

The environment is affected if Veeam Backup & Replication version 12.0.0.1402 through 12.2.0.333 is installed and low-privileged authenticated users have access to file deletion functionality via the web console or API.

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

Implement strict input validation and authorization checks on all file operations, ensuring low-privileged users can only delete files within their designated directories and cannot manipulate path traversal sequences or special characters to access protected filesystem locations.

Recommended fix High confidence

12.2.0.334 or later in the 12.2.x branch

  1. 1. Verify current Veeam Backup & Replication version by opening the Veeam Backup & Replication console and checking Help > About, or running Get-VBRServerInfo in PowerShell
  2. 2. Review the Veeam Backup & Replication 12.2 release notes at www.veeam.com to understand new features and any pre-upgrade requirements
  3. 3. Create a configuration backup of the current installation: open Veeam Backup & Replication console, go to Backup Infrastructure > Global Settings > Configuration Backup, and click Backup Now
  4. 4. Download Veeam Backup & Replication version 12.2.0.334 or later from the Veeam Customer Portal
  5. 5. Run the installer on the Veeam Backup & Replication server and follow the upgrade wizard prompts
  6. 6. After upgrade completes, verify the version shows 12.2.0.334 or later in Help > About
  7. 7. Test critical backup and restore operations to confirm functionality

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
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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