CVE-2024-39715
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 code injection vulnerability that allows a low-privileged user with REST API access granted to remotely upload arbitrary files to the VSPC server using REST API, leading to remote code execution on VSPC server.
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 confidenceA code injection vulnerability in Veeam Service Provider Console (VSPC) allows a low-privileged user with REST API access to upload arbitrary files to the server, leading to remote code execution. The vulnerability stems from insufficient validation of file uploads via the REST API endpoint.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/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 Service Provider Console installationCheck for VSPC installation by looking for the service process 'Veeam.ServiceProvider.Console.exe' in Task Manager or under C:\Program Files\Veeam\Service Provider Console\Affected if VSPC is installed and running
-
Determine VSPC versionOpen Programs and Features in Windows Control Panel, find 'Veeam Service Provider Console', and note the version; or run Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Veeam Service Provider Console*'} | Select-Object DisplayVersionAffected if Version matches or precedes the vulnerable range (verify against vendor release notes for CVE-2024-39715)
-
Verify REST API service is enabledCheck if the VSPC REST API service is running and accessible by attempting a local request to https://localhost:4280/api/ or reviewing IIS bindings if VSPC uses IIS hostingAffected if REST API endpoint responds and is accessible over network
-
Review user accounts with API accessOpen VSPC administration console, navigate to Users or Accounts section, and list all users with REST API permissions; run Get-VSPAccess in PowerShell if VSPC cmdlets are availableAffected if Any low-privileged user account exists with REST API access enabled
-
Inspect file upload configurationCheck VSPC configuration files in the installation directory for upload validation settings; review web.config for upload-related parameters under the REST API virtual directoryAffected if File upload feature is enabled without strict file type or content validation
Environment is affected if VSPC is installed with REST API enabled and low-privileged users have API upload permissions, regardless of version status.
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.
From vendor dataApply vendor patches immediately, restrict REST API access to essential personnel only, implement strict file type and content validation on upload endpoints, and audit existing user permissions.
- Consultation8.0 h
- Implementation20.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39715 — 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-39715 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