CVE-2024-42452
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 to start an agent remotely in server mode and obtain credentials, effectively escalating privileges to system-level access. This allows the attacker to upload files to the server with elevated privileges. The vulnerability exists because remote calls bypass permission checks, leading to full system compromise.
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 a privilege escalation vulnerability in Veeam Backup & Replication where low-privileged users can start an agent remotely in server mode, bypassing permission checks. This allows them to obtain credentials and achieve system-level access, enabling unauthorized file uploads to the server with elevated privileges.
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 Veeam Backup & Replication versionOpen the Veeam Backup & Replication console, or use PowerShell with the VeeamPSSnapIn module and run Get-VBRServer, or check the Windows Registry under HKLM\SOFTWARE\Veeam\Veeam Backup & Replication for the Version keyAffected if The installed version falls within >= 12.0.0.1402 and < 12.3.0.310
-
Verify remote agent startup capabilityReview audit logs or security event logs on the Veeam server for remote agent start requests originating from low-privileged accounts. Check if the Veeam API or service ports (default 9392, 9393) accept connections that initiate agent operations from non-admin usersAffected if Low-privileged users without administrative rights can successfully invoke agent start commands remotely
-
Inspect user role assignmentsIn the Veeam console, navigate to Users and Roles to enumerate all assigned roles. Use the Veeam PowerShell cmdlets to query Get-VBRRole and check which users are assigned to limited roles versus Administrator rolesAffected if Users with Basic, Operator, or backup-only roles have the ability to start agents in server mode
-
Check for unauthorized file access patternsReview Veeam job logs and Windows Security event logs for file upload or restore operations performed by users who should not have elevated privileges. Examine if credential caching or session tokens were accessed unexpectedlyAffected if Evidence exists of file operations or credential access performed by non-administrative accounts through agent-based sessions
Your environment is affected if the installed Veeam Backup & Replication version is between 12.0.0.1402 and 12.3.0.310 and low-privileged users can remotely start the backup agent in server mode.
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 the vendor-supplied patch immediately to address the permission bypass. Until patched, restrict network access to Veeam services and minimize user privileges following least-privilege principles.
Veeam Backup & Replication 12.3.0.310 or later
- Ensure you have a complete backup of the Veeam Backup & Replication server configuration and all critical data before proceeding with any changes
- Review the Veeam Backup & Replication 12.3 release notes and upgrade documentation for compatibility requirements and known issues
- Download Veeam Backup & Replication version 12.3.0.310 or later from the official Veeam downloads portal (www.veeam.com)
- Test the upgrade in a non-production environment first to verify compatibility with your infrastructure
- Execute the upgrade installer on the Veeam Backup & Replication server following the standard upgrade procedure
- Verify the upgrade was successful by checking the version number in the Veeam console or via the About section
- Confirm that low-privileged users can no longer start agents remotely in server mode without proper authorization
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-42452 — 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-42452 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