CVE-2024-42456
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 platform allows a low-privileged user with a specific role to exploit a method that updates critical configuration settings, such as modifying the trusted client certificate used for authentication on a specific port. This can result in unauthorized access, enabling the user to call privileged methods and initiate critical services. The issue arises due to insufficient permission requirements on the method, allowing users with low privileges to perform actions that should require higher-level permissions.
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 a low-privileged user with a specific role can invoke a method that updates critical configuration settings, such as modifying trusted client certificates used for authentication on specific ports. The insufficient permission check allows unauthorized access to call privileged methods and initiate critical services.
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 installation and versionLocate the Veeam installation directory or check installed programs, then determine the exact version number (typically found in About section of Veeam console, registry, or program files)Affected if Installed version falls within >= 12.0.0.1402 and < 12.3.0.310
-
Review user role assignments in VeeamAccess the Users and Roles section in Veeam Backup & Replication console or configuration database, then enumerate all users and their assigned rolesAffected if Any user account with low or limited privileges (such as read-only or operator roles) exists alongside administrative accounts in the system
-
Identify users with access to configuration methodsExamine role permissions to determine which users can access configuration or certificate management methods, particularly those related to trusted client certificates and service settingsAffected if Users with non-administrative roles have permissions to invoke methods that modify critical configuration settings or trusted client certificates
-
Inspect trusted client certificate configurationReview the configuration settings for trusted client certificates on specific ports within Veeam Backup & Replication (check via console under Certificates or Backup Infrastructure settings)Affected if Trusted client certificates are configured and accessible for modification by users who should not have such access
A user is affected if they have Veeam Backup & Replication version 12.0.0.1402 through 12.2.x installed with any low-privileged user accounts present that may have access to configuration modification methods.
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 to restrict the vulnerable method to properly privileged users, and review/limit user role assignments until the patch is deployed.
Veeam Backup & Replication 12.3.0.310 or later
- 1. Confirm current Veeam Backup & Replication version by checking the About section in the Veeam console or using the Get-VBRBackupServer PowerShell cmdlet
- 2. If version is between 12.0.0.1402 and 12.3.0.310 (exclusive), plan for upgrade during a maintenance window
- 3. Perform a full backup of Veeam configuration before upgrading
- 4. Download Veeam Backup & Replication version 12.3.0.310 or later from the official Veeam download portal
- 5. Run the installer and follow the upgrade wizard, selecting the upgrade option
- 6. After upgrade completes, verify the new version is installed and services are running
- 7. Verify that low-privileged users can no longer modify trusted client certificate settings without proper authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-42456 — 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-42456 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