CVE-2021-42712
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 · uneditedSplashtop Streamer through 3.4.8.3 creates a Temporary File in a Directory with Insecure Permissions.
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 confidenceSplashtop Streamer through version 3.4.8.3 creates temporary files in a directory with insecure permissions, potentially allowing unprivileged local users to read, modify, or replace these files. This insecure temporary file handling (CWE-378/379) could lead to information disclosure or privilege escalation if the application trusts the contents of these files.
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.5.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.
-
Check installed Splashtop Streamer versionOpen Control Panel > Programs and Features, or right-click the Splashtop Streamer icon and select 'About'. Look for the version number in the application GUI or installer properties.Affected if Version shown is 3.4.8.3 or earlier, meaning it is lower than 3.5.0.0
-
Verify version via Windows RegistryRun 'regedit' and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\SplashtopStreamer (or HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\SplashtopStreamer). Check the 'DisplayVersion' value.Affected if The DisplayVersion value is less than 3.5.0.0
-
Identify Splashtop Streamer temp directoriesMonitor the process using Sysinternals Process Monitor while Splashtop Streamer is running, or check common temp locations such as %TEMP%, %APPDATA%, and the installation directory (typically C:\Program Files\Splashtop\Splashtop Streamer\) for subfolders named 'temp' or 'tmp'.Affected if Temp directories created by Splashtop Streamer exist on the system
-
Check temp directory permissionsRight-click the identified temp folder, go to Properties > Security, and examine the permissions. Verify if unprivileged users or the 'Users' group have Modify, Write, or Full Control permissions.Affected if Unprivileged users have Write or Modify access to directories where Splashtop Streamer creates temporary files
You are affected if Splashtop Streamer version is below 3.5.0.0 AND unprivileged users can write to the application's temp directories.
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.5.0.0
Update Splashtop Streamer to the latest patched version. If an immediate update is not feasible, restrict file system permissions on the temp directories used by the application and monitor for unauthorized access.
3.5.0.0 or later
- Navigate to the official Splashtop website (www.splashtop.com) and download Splashtop Streamer version 3.5.0.0 or later
- Uninstall the current version of Splashtop Streamer from the system
- Install the newly downloaded version (3.5.0.0 or later)
- Restart the system if prompted
- Verify the installed version matches or exceeds 3.5.0.0
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-2021-42712 — 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-2021-42712 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