CVE-2024-42053: Incorrect Default Permissions
Source CVE Database V5
Not known to be exploited · CVSS 7.8 High · fixed in 3.6.0.0 : patch affected systems soon.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.6.0.0
CVSS:3.1/AC:L/AV:L/A:H/C:H/I:H/PR:L/S:U/UI:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
Organizations should immediately upgrade Splashtop Streamer for Windows to version 3.6.0.0 or later, where this vulnerability is fixed. If upgrading is not immediately possible, restrict local user permissions to prevent untrusted users from writing to temporary directories used during installation. Implement application whitelisting and endpoint detection to monitor for unauthorized DLL loading or suspicious installer behavior. Use least privilege principles to limit local user rights and prevent unauthorized software installation. Additionally, conduct regular audits of file system permissions on temporary folders used by installers. Employ host-based intrusion prevention systems (HIPS) to detect and block DLL hijacking attempts. Finally, educate IT staff and users about the risks of local privilege escalation and ensure that remote access tools like Splashtop are kept up to date with security patches.
Description
The 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.