CVE-2024-42051
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.6.2.0 uses a temporary folder with weak permissions during installation. A local user can exploit this to escalate privileges to SYSTEM by replacing InstRegExp.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 versions before 3.6.2.0 creates a temporary folder during installation with weak permissions. A local unprivileged user can exploit this by replacing the InstRegExp.reg file in the insecure temp folder to achieve SYSTEM-level code execution when the installer runs.
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.6.2.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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/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.
-
Check if Splashtop Streamer is installedOpen Programs and Features (appwiz.cpl) or check registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Splashtop Streamer entryAffected if No Splashtop Streamer entry is found - the product is not installed
-
Identify installed versionIn Programs and Features, locate Splashtop Streamer and note the Version column, or query the uninstall registry key for the DisplayVersion valueAffected if The displayed version is lower than 3.6.2.0 (for example, 3.6.1.0, 3.5.x, etc.)
-
Locate installer temporary foldersSearch the file system for folders named with patterns like 'Splashtop' or 'MSI' in user-accessible temp locations (check %TEMP%, %LOCALAPPDATA%\Temp, and common installer working directories)Affected if Folders with weak permissions or leftover installation files (such as InstRegExp.reg) are found in unprotected locations
-
Review recent installation activityCheck Windows Event Viewer under Windows Logs\Application for MSI Installer events related to Splashtop, or look for recent installer log files in %TEMP%Affected if Installation events indicate a version prior to 3.6.2.0 was recently run on the system
A system is affected if Splashtop Streamer for Windows version 3.6.2.0 or earlier is or was installed, and the installer temp folder with weak permissions may still exist or was recently created.
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.6.2.0
Upgrade Splashtop Streamer for Windows to version 3.6.2.0 or later, which addresses the weak temporary folder permissions. Avoid running installers in multi-user or untrusted environments until patched.
Splashtop Streamer for Windows 3.6.2.0 or later
- Identify all Windows systems with Splashtop Streamer installed in your environment
- Check the current version of Splashtop Streamer on each system (found in Programs and Features or the application's About/Help section)
- For any system running a version before 3.6.2.0, download the Splashtop Streamer installer version 3.6.2.0 or later from the official Splashtop website or your organization's software repository
- Follow your organization's standard procedure to upgrade the software, ensuring you have appropriate backup and rollback capabilities
- After upgrading, verify the installed version shows 3.6.2.0 or higher to confirm the remediation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-42051 — 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-42051 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