Pcoip Soft ClientApplication · Teradici
CVE-2021-25689
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 · uneditedAn out of bounds write in Teradici PCoIP soft client versions prior to version 20.10.1 could allow an attacker to remotely execute code.
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 · moderate confidenceAn out-of-bounds write vulnerability in Teradici PCoIP soft client versions before 20.10.1 allows attackers to write data beyond allocated memory boundaries, which can be exploited to achieve remote code execution on affected systems.
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
Pcoip Soft ClientApplication
<= 20.10.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm Teradici PCoIP Soft Client is installedCheck the installed programs list on the system, or run 'Get-WmiObject -Class Win32_Product' to list installed software and search for 'PCoIP' or 'Teradici'Affected if Teradici PCoIP Soft Client appears in the installed software list
-
Identify the installed version numberIn Windows: Navigate to Control Panel > Programs and Features, find Teradici PCoIP Soft Client, and note the version shown in the Version column. Alternatively, right-click the application executable and view Properties > Details for version information.Affected if Version displayed is 20.10.0 or earlier
-
Query version via command lineOpen Command Prompt or PowerShell and run 'wmic product where "name like '%PCoIP%'" get version,name' or use 'Get-ItemProperty' on the installation directory if knownAffected if The reported version is 20.10.0 or lower
-
Compare against vulnerable version rangeCompare the identified version number to the affected range: any version <= 20.10.0Affected if The installed version is 20.10.0 or any earlier version such as 20.09.x, 20.08.x, etc.
The environment is affected if Teradici PCoIP Soft Client version 20.10.0 or any earlier version is installed on the system.
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 · scopedUpgrade Teradici PCoIP soft client to version 20.10.1 or later to address the vulnerability.
20.10.1
- Navigate to the Teradici support portal or official download page to obtain PCoIP Soft Client version 20.10.1 or later
- Download the installer for the fixed version (20.10.1)
- Close any running instances of the PCoIP Soft Client
- Run the installer and follow the prompts to upgrade to version 20.10.1 or newer
- After installation, verify the version by checking the client About or version information
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Pcoip Soft Client
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-25689 — 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-25689 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