CVE-2021-25693
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 attacker may cause a Denial of Service (DoS) in multiple versions of Teradici PCoIP Agent via a null pointer dereference.
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 confidenceA null pointer dereference vulnerability in Teradici PCoIP Agent allows an unauthenticated attacker to crash the agent process, causing a Denial of Service. The vulnerability exists in multiple versions of the PCoIP Agent software.
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>= 20.10, < 20.10.6>= 21.01, < 21.01.5>= 21.03, < 21.03.1CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Identify if PCoIP Agent is installedOn Windows, check Add/Remove Programs or the Program Files directory for Teradici PCoIP folders. On Linux, run 'dpkg -l | grep -i pcoip' or 'rpm -qa | grep -i pcoip'. Check running processes for pcoip.exe or pcoip-agentAffected if PCoIP Agent software is found installed or running on the system
-
Locate the installed version numberRun 'pcoip-agent --version' from command line if available, or right-click the pcoip-agent executable and select Properties > Details to view FileVersion. On Windows, also check the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for PCoIP entriesAffected if Version number is retrieved from the agent installation
-
Compare version against affected rangesIf version starts with 20.10, ensure it is less than 20.10.6. If 21.01, ensure less than 21.01.5. If 21.03, ensure less than 21.03.1Affected if Installed version is 20.10.0-20.10.5, OR 21.01.0-21.01.4, OR 21.03.0
System is affected if Teradici PCoIP Agent is installed and the version matches any of the three vulnerable ranges: >=20.10 and <20.10.6, >=21.01 and <21.01.5, or >=21.03 and <21.03.1
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.
From vendor data20.10.621.01.521.03.1
Contact Teradici for patched versions of PCoIP Agent and apply available updates. Implement network-level access controls to limit exposure to untrusted sources until patches are applied.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-25693 — 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-25693 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