CVE-2024-38650
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 · uneditedAn authentication bypass vulnerability can allow a low privileged attacker to access the NTLM hash of service account on the 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 confidenceAn authentication bypass vulnerability in Veeam Service Provider Console (VSPC) allows a low-privileged attacker to access NTLM hashes of service accounts. The NTLM hash exposure enables credential cracking offline or potential pass-the-hash attacks for lateral movement within the environment.
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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/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.
-
Confirm VSPC installation and running statusOn the server, open Services.msc and look for 'Veeam Service Provider Console' service, or run 'Get-Service -Name Veeam*' in PowerShell to check if VSPC services are running.Affected if VSPC service is installed and running on the system
-
Identify installed VSPC versionOpen Windows Registry and navigate to HKLM\SOFTWARE\Veeam\Veeam Service Provider Console\ or check the web interface login page footer for version information. Alternatively, check Programs and Features for 'Veeam Service Provider Console' entry.Affected if Version cannot be determined or falls within unpatched version ranges
-
Verify web console accessibilityOpen a browser and attempt to access the VSPC web interface (default port 4280 or 4282). Check if the login page loads successfully, indicating the service is reachable.Affected if VSPC web interface is accessible from network locations
-
Review authentication logs for anomaliesOn the VSPC server, navigate to the log directory (typically C:\ProgramData\Veeam\ServiceProviderConsole\Logs\) and review authentication and audit logs for unauthorized access attempts by low-privilege users, especially after the patch release date.Affected if Logs show unexpected authentication events from low-privileged accounts accessing service account credential data
A system is affected if VSPC is running with an unpatched version and the web interface is network-accessible, allowing a low-privileged attacker to obtain NTLM hashes of service accounts through the authentication bypass.
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-supplied patches for CVE-2024-38650 immediately; until patched, monitor VSPC server access logs for unauthorized authentication attempts and consider network segmentation to limit exposure of the service account credentials.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-38650 — 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-38650 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