CVE-2024-40713
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 that allows a user who has been assigned a low-privileged role within Veeam Backup & Replication to alter Multi-Factor Authentication (MFA) settings and bypass MFA.
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 confidenceThis is an insecure privilege escalation vulnerability in Veeam Backup & Replication where the role-based access control (RBAC) fails to properly restrict low-privileged users from accessing MFA configuration settings. A user with a low-privileged role can alter MFA settings (such as disabling MFA or adding their own method), effectively bypassing the MFA security control intended for higher-privileged accounts.
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.2.0.334CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Veeam Backup & Replication versionOpen the Veeam Backup & Replication console, go to Help > About, or run 'veeam_version.exe' from the installation directory to retrieve the exact build numberAffected if The reported version is lower than 12.2.0.334 (for example, 12.1.x or 12.0.x)
-
Confirm RBAC is in use with non-administrative rolesIn the console, navigate to Users and Roles > Roles to review defined role assignments. Check if any users or groups are assigned roles other than 'Administrator' (such as 'Backup Operator' or 'Read-Only')Affected if Low-privileged users or custom roles exist in the system beyond just full Administrators
-
Verify whether low-privileged users can access MFA configurationLog in as a non-administrator user (or use the test button for a custom role) and attempt to navigate to the MFA settings area (typically under Administration > MFA or user profile security settings). Observe whether access is granted without rejectionAffected if A user with limited role permissions can open or modify MFA settings when they should not have authorization
-
Review audit logs for unexpected MFA changesIn the console, go to History or Audit Logs and filter for events related to MFA configuration changes (such as 'MFA disabled', 'MFA method added', or 'MFA settings modified'). Look for entries made by low-privileged accountsAffected if Audit logs show MFA settings were changed by users without Administrator privileges
-
Check current MFA enforcement statusNavigate to Administration > MFA or the global security settings to see if MFA is enabled and required. Also verify whether the setting can be toggled by a low-privileged test accountAffected if MFA is not properly enforced, or low-privileged users have the ability to disable or alter MFA settings
You are affected if your Veeam Backup & Replication version is below 12.2.0.334 and you have non-administrator users who can access or modify MFA settings they should not be authorized to change.
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.2.0.334
Apply the vendor patch when released. Until then, restrict low-privileged user access to the Veeam Backup & Replication console and monitor audit logs for unauthorized changes to MFA settings.
Veeam Backup & Replication 12.2.0.334 or later
- Obtain Veeam Backup & Replication version 12.2.0.334 or later from the official Veeam download portal at www.veeam.com
- Review the Veeam Backup & Replication 12.2 release notes and upgrade documentation for version 12.2.0.334
- Schedule a maintenance window and ensure full backups of all protected data exist
- Stop all Veeam services or follow the official upgrade procedure for your deployment type
- Run the Veeam Backup & Replication installer and follow the on-screen prompts to upgrade to version 12.2.0.334 or later
- After upgrade completes, verify all Veeam services are running properly
- Log in to the Veeam console and verify MFA settings are properly configured and enforced
- Confirm low-privileged users can no longer modify MFA settings without proper authorization
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-40713 — 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-40713 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