CVE-2024-40717
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 · uneditedA vulnerability in Veeam Backup & Replication allows a low-privileged user with certain roles to perform remote code execution (RCE) by updating existing jobs. These jobs can be configured to run pre- and post-scripts, which can be located on a network share and are executed with elevated privileges by default. The user can update a job and schedule it to run almost immediately, allowing arbitrary code execution on the server.
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 confidenceIn Veeam Backup & Replication, low-privileged users with certain roles can modify existing backup jobs to add or alter pre- and post-scripts. These scripts run from network shares with elevated privileges, and by scheduling the modified job to run immediately, an attacker can achieve arbitrary code execution on the server.
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>= 12.0.0.1402, < 12.3.0.310CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Veeam Backup & Replication versionCheck the installed version of Veeam Backup & Replication in the product UI or registry, or use the Veeam PowerShell cmdlet Get-VBRVersion or the About section in the consoleAffected if The installed version is 12.0.0.1402 or higher but lower than 12.3.0.310
-
Review user role assignmentsIn the Veeam console, navigate to Users and Roles or use Get-VBRRoleAssignment to list all users and their assigned roles. Identify accounts that are not Domain Admins or equivalent high-privilege usersAffected if Any low-privileged user account is assigned a role that permits modification of backup job settings
-
Enumerate backup jobs with pre- or post-scripts configuredIn the Veeam console, review each backup job's Properties and look for the Scripts section in the Guest Processing settings, or use PowerShell to query jobs with Get-VBRJob and inspect the ScriptConfigurationAffected if Any backup job has pre-script or post-script paths configured pointing to custom scripts
-
Verify low-privileged user access to job modificationAttempt to modify a backup job configuration using a low-privileged test account, or review role permissions to confirm which roles include Job Edit or Job Configure rightsAffected if Users with low-privileged roles can successfully edit backup job properties including script configurations
You are affected if your Veeam version is 12.0.0.1402 through 12.3.0.310 and any non-admin user has a role permitting backup job modification, especially if jobs have custom pre/post scripts configured.
Generated from the published advisory. Verify against your own configuration.
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 · scoped12.3.0.310
Restrict or disable the ability for low-privileged users to modify backup job scripts and schedule configurations. Apply vendor patches when available and audit existing user roles for excessive permissions.
Veeam Backup & Replication 12.3.0.310 or later
- 1. Ensure you have a complete backup of your Veeam Backup & Replication configuration and verify your disaster recovery plan.
- 2. Download Veeam Backup & Replication version 12.3.0.310 or later from the official Veeam download portal (www.veeam.com).
- 3. Review the Veeam Upgrade Guide for version 12.3 to understand any prerequisites and ensure your environment meets the requirements.
- 4. Run the Veeam Backup & Replication installer and select the Upgrade option.
- 5. Follow the on-screen prompts to complete the upgrade process.
- 6. After upgrade, verify that the Veeam services start successfully and the console is accessible.
- 7. Confirm that low-privileged users can no longer modify job scripts without proper authorization by testing with a limited-role account.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-40717 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-40717 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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