dbcve.org
Veeam Backup \& ReplicationApplication · Veeam

CVE-2024-42457

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-04
Fix available
A fix is available. Upgrade to 12.3.0.310 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A vulnerability in Veeam Backup & Replication allows users with certain operator roles to expose saved credentials by leveraging a combination of methods in a remote management interface. This can be achieved using a session object that allows for credential enumeration and exploitation, leading to the leak of plaintext credentials to a malicious host. The attack is facilitated by improper usage of a method that allows operators to add a new host with an attacker-controlled IP, enabling them to retrieve sensitive credentials in plaintext.

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 confidence

An authenticated operator role vulnerability in Veeam Backup & Replication allows users with certain operator roles to add new hosts with attacker-controlled IP addresses through a remote management interface session object, enabling retrieval and exfiltration of stored plaintext credentials.

MitigationRestrict operator role permissions to limit host addition capabilities, implement network segmentation to prevent credential exfiltration to untrusted hosts, and apply vendor-supplied patches when available.

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
Veeam Backup \& ReplicationApplication
Affected:>= 12.0.0.1402, < 12.3.0.310

CVSS 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Veeam Backup & Replication version
    Open the Veeam Backup & Replication console, go to Help > About, or run 'vbr_version' command in PowerShell with VeeamPSSnapin loaded
    Affected if Version is 12.0.0.1402 or higher but lower than 12.3.0.310
  2. Check for operator role configurations
    In the Veeam console, navigate to Users and Roles > Roles to list all defined operator roles
    Affected if Any operator role exists with permissions that allow adding or managing hosts
  3. Verify operator account assignments
    In the console, go to Users and Roles > Users to see which operators are assigned to which roles
    Affected if Operators are assigned to roles that permit host addition capabilities
  4. Inspect remote management interface configurations
    Check the configuration for any remote management interface session objects that could be used to specify host IP addresses
    Affected if Remote management sessions are configured and accessible to operator accounts

Your environment is affected if Veeam Backup & Replication version is 12.0.0.1402 or higher but below 12.3.0.310 AND operator roles with host addition permissions exist in the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 12.3.0.310 or later
Fixed in 12.3.0.310
Interim mitigation

Restrict operator role permissions to limit host addition capabilities, implement network segmentation to prevent credential exfiltration to untrusted hosts, and apply vendor-supplied patches when available.

Recommended fix Moderate confidence

Veeam Backup & Replication 12.3.0.310 or later

  1. 1. Identify the current installed version of Veeam Backup & Replication by checking the About section in the Veeam Backup & Replication console.
  2. 2. If the installed version is between 12.0.0.1402 and 12.3.0.310 (exclusive), plan for an upgrade to version 12.3.0.310 or later.
  3. 3. Review Veeam Upgrade Best Practices documentation for your environment before initiating the upgrade.
  4. 4. Perform a full backup of your Veeam configuration as a precautionary measure.
  5. 5. Download the latest Veeam Backup & Replication version 12.3 or later from the Veeam downloads portal.
  6. 6. Execute the upgrade installer and follow the on-screen prompts to complete the update.
  7. 7. After upgrade, verify the installation was successful and test critical backup/restore functions.
Caveat Review Veeam 12.3 release notes for any configuration or feature changes that may affect your environment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Veeam Backup \& Replication Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-42457 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-42457 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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