CVE-2024-42053
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.0.0 uses a temporary folder with weak permissions during installation. A local user can exploit this to escalate privileges to SYSTEM by placing a version.dll file in the folder.
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 unprivileged user can place a malicious version.dll in this folder, which gets loaded by the installer process running with SYSTEM privileges, resulting in privilege escalation.
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.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
- 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.
-
Verify Splashtop Streamer is installedCheck for Splashtop Streamer installation in registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or look for the application in C:\Program Files\Splashtop\Splashtop StreamerAffected if Splashtop Streamer is found on the system
-
Retrieve installed versionOpen Windows Registry and locate the DisplayVersion value under the Splashtop Streamer uninstall key, or right-click the installed executable and select Properties to view the File VersionAffected if The version displayed is less than 3.6.0.0
-
Check for legacy installer filesSearch for any .msi installer files for Splashtop Streamer in download folders, shared drives, or software deployment repositoriesAffected if An older installer version (< 3.6.0.0) is present on the system
-
Identify temp folder permissions during installationWhen the MSI installer runs, use Process Monitor or observe the %TEMP% or C:\Users\<user>\AppData\Local\Temp folder created by the installer for extraction. Check folder permissions with icaclsAffected if The installer extraction folder allows standard users write access and the installer runs with elevated privileges
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.0.0
Upgrade to Splashtop Streamer version 3.6.0.0 or later, which addresses the insecure temporary folder usage.
3.6.0.0
- Navigate to the official Splashtop download page or the Splashtop Business support portal to obtain the latest Streamer installer
- Download the Splashtop Streamer installer version 3.6.0.0 or later
- Run the installer with administrator privileges to upgrade the existing installation
- Follow the on-screen prompts to complete the upgrade
- Verify the installed version by checking the Streamer application or add/remove programs to confirm version 3.6.0.0 or higher is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-42053 — 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-42053 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