CVE-2024-42050
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 · uneditedThe MSI installer for Splashtop Streamer for Windows before 3.7.0.0 uses a temporary folder with weak permissions during installation. A local user can exploit this to escalate privileges to SYSTEM via an oplock on CredProvider_Inst.reg.
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 confidenceThe MSI installer for Splashtop Streamer for Windows creates a temporary folder with weak permissions during installation. A local attacker can exploit this by placing a malicious file (specifically using an oplock on CredProvider_Inst.reg) in the weakly-protected temp folder to achieve privilege escalation to SYSTEM.
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< 3.7.0.0CVSS 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
- Local
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/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.
-
Verify Splashtop Streamer is installedOpen Windows Settings > Apps & Features (or run 'appwiz.cpl') and search for 'Splashtop Streamer' in the installed programs listAffected if Splashtop Streamer does not appear in the installed programs list, then the vulnerability does not apply
-
Check installed version numberIn Apps & Features, click on Splashtop Streamer and view the Version field, or open Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{Splashtop Streamer GUID} to find the DisplayVersion valueAffected if The displayed version is less than 3.7.0.0 (for example 3.6.x, 3.5.x, etc.)
-
Check for previous installation evidenceSearch for 'Splashtop' folders in Program Files or Program Files (x86) directory and locate any version information in file propertiesAffected if Found version information showing a version below 3.7.0.0
If Splashtop Streamer for Windows is installed with a version lower than 3.7.0.0, the environment is affected by this vulnerability because the installer used weak temporary folder permissions during setup.
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 · scoped3.7.0.0
Upgrade Splashtop Streamer for Windows to version 3.7.0.0 or later, which addresses the insecure temporary folder usage during installation.
3.7.0.0
- Download the Splashtop Streamer installer version 3.7.0.0 or later from the official Splashtop support site (support-splashtopbusiness.splashtop.com)
- Ensure any running Splashtop Streamer applications are closed before upgrading
- Run the updated MSI installer with appropriate administrator privileges
- Follow the on-screen prompts to complete the installation
- Verify the installation was successful by checking the Streamer version in the application or Add/Remove Programs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-42050 — 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-42050 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