StreamerApplication · Splashtop

CVE-2024-42051

HIGH · 7.8 CVSS v3.1 Published 2024-07-28
Fix available
A fix is available. Upgrade to 3.6.2.0 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
The 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 confidence

The 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.

MitigationUpgrade 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.

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
StreamerApplication
Affected:< 3.6.2.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Splashtop Streamer is installed
    Open Programs and Features (appwiz.cpl) or check registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Splashtop Streamer entry
    Affected if No Splashtop Streamer entry is found - the product is not installed
  2. Identify installed version
    In Programs and Features, locate Splashtop Streamer and note the Version column, or query the uninstall registry key for the DisplayVersion value
    Affected if The displayed version is lower than 3.6.2.0 (for example, 3.6.1.0, 3.5.x, etc.)
  3. Locate installer temporary folders
    Search 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
  4. Review recent installation activity
    Check 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.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.6.2.0 or later
Fixed in 3.6.2.0
Interim mitigation

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.

Recommended fix High confidence

Splashtop Streamer for Windows 3.6.2.0 or later

  1. Identify all Windows systems with Splashtop Streamer installed in your environment
  2. Check the current version of Splashtop Streamer on each system (found in Programs and Features or the application's About/Help section)
  3. 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
  4. Follow your organization's standard procedure to upgrade the software, ensuring you have appropriate backup and rollback capabilities
  5. 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.

Fix this in Streamer Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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 locally
dbcve dependency scanner

Check 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-42051 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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