CVE-2024-45206
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 Service Provider Console has been identified, which allows to perform arbitrary HTTP requests to arbitrary hosts of the network and get information about internal resources.
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 Service Provider Console (VSPC) contains an Server-Side Request Forgery (SSRF) vulnerability that allows authenticated attackers to make arbitrary HTTP requests to internal network hosts and retrieve information about internal resources. This could allow enumeration of internal services, cloud metadata endpoints, or other sensitive infrastructure.
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>= 7.0.0.12777, < 8.1.0.21377CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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.
-
Confirm VSPC installation and versionOpen Windows Registry and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Service Provider Console or check the About page in the VSPC web console. The version is displayed as a build number.Affected if The installed version is greater than or equal to 7.0.0.12777 and less than 8.1.0.21377
-
Verify VSPC web service is runningOpen Services.msc and check if 'Veeam Service Provider Console' service is running, or check if port 4280 (default VSPC web interface) is listening via netstat -an | findstr 4280Affected if The VSPC web service is running and accessible, enabling the SSRF attack surface
-
Check for existing user accountsLog into VSPC web console and navigate to Users or Accounts section to enumerate valid authentication credentials, or check local Windows users that have VSPC accessAffected if Any valid user account exists in VSPC, as the SSRF requires authentication to exploit
-
Review outbound HTTP traffic from VSPC serverUse Windows Firewall with Advanced Security to audit outbound rules, or review network logs for HTTP/HTTPS requests originating from the VSPC server to internal IP ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16)Affected if Unusual outbound HTTP requests to internal network targets are observed, indicating potential exploitation
A system is affected if Veeam Service Provider Console version 7.0.0.12777 through 8.1.0.21376 is installed, the VSPC web service is running, and the server has network access to internal resources that could be targeted via SSRF.
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 · scoped8.1.0.21377
Apply the vendor patch from Veeam when available. As a compensating control, implement strict network segmentation to restrict what targets the VSPC server can reach, and monitor for unusual outbound HTTP traffic patterns from the VSPC server.
8.1.0.21377 or later
- Verify current Veeam Service Provider Console version is >= 7.0.0.12777 and < 8.1.0.21377
- Download Veeam Service Provider Console version 8.1.0.21377 or later from the official Veeam download portal
- Review Veeam upgrade documentation and ensure prerequisites are met
- Execute the upgrade following standard Veeam upgrade procedures
- Verify the upgrade completed successfully and the new version is running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45206 — 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-45206 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