dbcve.org
Veeam Backup \& ReplicationApplication · Veeam

CVE-2024-40712

HIGH · 7.8 CVSS v3.1 Published 2024-09-07
Fix available
A fix is available. Upgrade to 12.2.0.334 or later.
See remediation →
80/100
Remediation priority · High
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 path traversal vulnerability allows an attacker with a low-privileged account and local access to the system to perform local privilege escalation (LPE).

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

A path traversal vulnerability in the affected system allows a user with low-level privileges and local system access to manipulate file paths and escape intended directory restrictions, ultimately escalating their privileges to administrator or root level.

MitigationImplement strict input validation and canonicalization on all file path parameters, use allow-lists for permitted paths, and ensure proper filesystem permissions are enforced to prevent privilege escalation.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 Backup & Replication is installed
    Check for Veeam Backup & Replication installation on the system. On Windows, look in Program Files\Veeam or check the Windows Services list for Veeam services. On Linux, check /opt/veeam or systemctl list-unit-files for veeam services.
    Affected if Veeam Backup & Replication is not installed on the system.
  2. Determine the installed version number
    On Windows, open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup & Replication\ or right-click the Veeam icon and select About. On Linux, run 'veeam --version' or check /opt/veeam/veeam/br_info.xml.
    Affected if Unable to determine the version number.
  3. Compare version against affected range
    If version is found, compare it to the affected range: any version below 12.2.0.334 is vulnerable. Note that version 12.2.0.334 itself or higher is not affected.
    Affected if Installed version is less than 12.2.0.334.
  4. Check for presence of low-privilege user accounts
    Review user accounts on the system that have local access but limited privileges. On Windows, use 'net user' or Local Users and Groups (lusrmgr.msc). On Linux, check /etc/passwd for non-root users with shell access.
    Affected if Low-privilege local users exist on the system.
  5. Verify file permission configurations
    Examine file system permissions on Veeam installation directories and backup storage locations. Check if low-privilege users have write access to directories outside their intended scope. Use icacls (Windows) or ls -la (Linux) on Veeam directories.
    Affected if Low-privilege users have excessive file system access beyond their designated directories.

A system is affected if Veeam Backup & Replication version is installed and that version is below 12.2.0.334, combined with the presence of low-privilege local users who could potentially exploit the path traversal to escalate privileges.

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 canonicalization on all file path parameters, use allow-lists for permitted paths, and ensure proper filesystem permissions are enforced to prevent privilege escalation.

Recommended fix Moderate confidence

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

  1. Verify current Veeam Backup & Replication version via Veeam Console or installed programs list
  2. Download Veeam Backup & Replication version 12.2.0.334 or later from the official Veeam download portal (www.veeam.com)
  3. Review Veeam's official upgrade guide and release notes for version 12.2.x
  4. Ensure all critical backups are completed and verified before proceeding
  5. Stop all Veeam services or follow the recommended maintenance window procedure from Veeam documentation
  6. Run the installer for version 12.2.0.334 or later with appropriate administrative privileges
  7. Follow the on-screen upgrade wizard instructions, selecting upgrade/repair option
  8. Restart the server if prompted by the installer
Caveat Review Veeam 12.2 release notes for any configuration or feature changes; test in non-production environment first

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 / 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-40712 — 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-40712 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