CVE-2024-42453
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 Veeam Backup & Replication allows low-privileged users to control and modify configurations on connected virtual infrastructure hosts. This includes the ability to power off virtual machines, delete files in storage, and make configuration changes, potentially leading to Denial of Service (DoS) and data integrity issues. The vulnerability is caused by improper permission checks in methods accessed via management services.
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 confidenceVeeam Backup & Replication contains an authorization bypass vulnerability where low-privileged users can invoke management service methods without proper permission validation. This allows authenticated but low-privilege users to perform high-impact operations including powering off virtual machines, deleting storage files, and making infrastructure configuration changes, resulting in potential DoS and data integrity compromise.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Veeam Backup & Replication versionOpen Veeam Backup & Replication console, go to Help > About, or run 'Get-VBRVersion' in PowerShell if VeeamPSSnapin is installed. Compare the version number against the affected range: 12.0.0.1402 <= version < 12.3.0.310Affected if The installed version falls within 12.0.0.1402 through 12.3.0.309 (inclusive)
-
Identify low-privilege user accountsIn Veeam Backup & Replication, navigate to Users and Roles (or Inventory > Security > Users). Review user accounts and their assigned roles. Look for users assigned to roles with limited permissions such as 'Viewer', 'Operator', 'Backup Operator', or custom roles with restricted accessAffected if Low-privilege user accounts exist in the Veeam environment
-
Review audit logs for unauthorized VM operationsOpen Veeam Backup & Replication, go to History > Audit. Filter logs for events involving VM power operations (Power Off, Power On, Restart) and check if the initiator is a low-privilege user accountAffected if Audit logs show VM power operations performed by users without administrative privileges
-
Check audit logs for storage file deletion or infrastructure changesIn the Veeam console, go to History > Audit. Look for events such as 'Delete Backup', 'Remove from Backup', 'Delete Repository', or infrastructure configuration changes (Add/Remove/Modify Hosts, Datastores, Proxies) initiated by low-privilege usersAffected if Audit logs reveal storage deletion or infrastructure configuration changes made by non-administrative users
Your environment is affected if the installed Veeam Backup & Replication version is between 12.0.0.1402 and 12.3.0.309 AND low-privileged users have performed administrative operations visible in audit logs.
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
Apply vendor-provided patches for CVE-2024-42453 immediately. In the interim, restrict low-privileged user access to Veeam Backup & Replication and monitor for unauthorized infrastructure manipulation through audit logs.
Veeam Backup & Replication 12.3.0.310 or later
- 1. Identify current Veeam Backup & Replication version by checking About section in the console or via PowerShell with Get-VBRServerInfo
- 2. Review release notes for version 12.3.0.310 (or latest 12.x release) to understand new features and any prerequisites
- 3. Create a backup of the Veeam configuration using the built-in Configuration Backup feature
- 4. Schedule a maintenance window as upgrades require service downtime
- 5. Download the updated installer from Veeam.com (Veeam Backup & Replication version 12.3.0.310 or later)
- 6. Run the installer and follow the upgrade wizard, selecting 'Upgrade' when prompted
- 7. Allow the upgrade to complete and services to restart
- 8. Verify the version now shows 12.3.0.310 or later using Get-VBRServerInfo
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-42453 — 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-42453 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