CVE-2024-42455
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 connect to remoting services and exploit insecure deserialization by sending a serialized temporary file collection. This exploit allows the attacker to delete any file on the system with service account privileges. The vulnerability is caused by an insufficient blacklist during the deserialization process.
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 insecure deserialization vulnerability in its remoting services. A low-privileged attacker can send a serialized temporary file collection that bypasses an insufficient blacklist, allowing execution that deletes arbitrary files with service account 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
- 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' PowerShell command if remote scripting is enabled. Compare the version number against the vulnerable range: 12.0.0.1402 through 12.3.0.309.Affected if Version is 12.0.0.1402 or higher but lower than 12.3.0.310 (or 12.3.0.309 and below).
-
Verify remoting services are enabledCheck if the Veeam Remote Proxy or Enterprise Manager remoting services are running. In Windows Services, look for 'Veeam Remote Proxy' service status, or check network listeners on ports used by Veeam remoting (typically 9392/9393).Affected if Remoting services are enabled and listening for incoming connections.
-
Confirm network exposure of remoting interfaceRun 'netstat -an | findstr 9392' or 'netsh interface ipv4 show tcpconnections' to check if port 9392 (default remoting port) is bound to external interfaces. Verify the service is not restricted to localhost or trusted internal networks.Affected if Remoting service port is listening on 0.0.0.0 or an exposed network interface.
The environment is affected if Veeam Backup & Replication version is between 12.0.0.1402 and 12.3.0.309 inclusive, and remoting services are enabled and network-accessible.
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 Veeam Backup & Replication. If immediate patching is not possible, restrict network access to remoting services and monitor for suspicious serialized traffic.
12.3.0.310 or later (12.3.x branch)
- 1. Download Veeam Backup & Replication version 12.3.0.310 or later from the official Veeam website (www.veeam.com)
- 2. Review Veeam's release notes and upgrade documentation for version 12.3.x
- 3. Schedule a maintenance window and perform a full backup of your Veeam configuration
- 4. Run the installer and follow the upgrade wizard to update to the fixed version
- 5. Verify the upgrade was successful and test that Veeam Backup & Replication services are running correctly
- 6. Confirm the vulnerability is remediated by reviewing the applied version matches or exceeds 12.3.0.310
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-42455 — 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-42455 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