CVE-2024-42451
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 low-privileged users to leak all saved credentials in plaintext. This is achieved by calling a series of methods over an external protocol, ultimately retrieving the credentials using a malicious setup on the attacker's side. This exposes sensitive data, which could be used for further attacks, including unauthorized access to systems managed by the platform.
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 confidenceVeeam Backup & Replication contains an access control vulnerability where low-privileged users can retrieve all stored credentials in plaintext by chaining multiple method calls over an external protocol. The attack exploits insufficient authorization checks during the credential retrieval process, allowing any authenticated user to access sensitive credential data that should be restricted to administrators.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Veeam Backup & Replication versionOpen the Veeam Backup & Replication console and navigate to Help > About, or check Programs and Features in Windows for 'Veeam Backup & Replication' entry to view the installed version numberAffected if The installed version is 12.0.0.1402 or higher but lower than 12.3.0.310
-
Review audit logs for credential access eventsAccess the Veeam audit logs or Windows Event Viewer and search for events related to credential retrieval, credential management, or stored credentials access. Look for patterns indicating bulk credential exports or accesses by non-administrator accountsAffected if Non-administrator users have accessed credential retrieval functions or exported stored credentials, especially in bulk operations
-
Examine user account permissionsOpen the Veeam Backup & Replication console and review the assigned roles and permissions for all non-administrator user accounts. Check which users have been granted access to credential storage or backup infrastructure settingsAffected if Low-privilege users have permissions that allow them to invoke credential retrieval methods or access credential storage features
-
Check for unusual API or protocol method callsReview network logs, proxy logs, or Veeam service logs for patterns of chained method calls to external protocol handlers that could indicate the exploitation technique. Look for sequences of calls that together bypass authorization checksAffected if There are log entries showing rapid sequential method calls from authenticated non-admin sessions that retrieve credential data that should require elevated privileges
-
Identify accounts that accessed credentialsRun a report or query on the backup server to list all authenticated user sessions that accessed the credential store within the vulnerability timeframe. Cross-reference with your list of administrator accountsAffected if Any authenticated non-administrator account successfully accessed the credential storage or retrieved plaintext credentials
You are affected if your Veeam Backup & Replication version falls within 12.0.0.1402 through 12.3.0.309 and you have non-administrator users who were able to retrieve stored credentials or access credential management functions.
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 for CVE-2024-42451 immediately. Until patched, limit user permissions to the minimum required and monitor for unusual credential access patterns or API calls.
12.3.0.310 or later
- Upgrade Veeam Backup & Replication to version 12.3.0.310 or later to remediate the vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-42451 — 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-42451 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