CVE-2021-25694
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 · uneditedTeradici PCoIP Graphics Agent for Windows prior to 21.03 does not validate NVENC.dll. An attacker could replace the .dll and redirect pixels elsewhere.
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 confidenceTeradici PCoIP Graphics Agent for Windows prior to version 21.03 fails to validate the integrity of NVENC.dll, allowing an attacker to replace the legitimate DLL with a malicious version that can redirect captured display pixels to an unauthorized location.
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< 21.03CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Identify installed PCoIP Graphics Agent versionOpen Windows Control Panel > Programs and Features, or run 'Get-ItemProperty' on the installation directory, or check the program executable properties for version informationAffected if The installed version is lower than 21.03 (for example, 21.01, 20.x, or earlier)
-
Locate NVENC.dll in the PCoIP installation directoryNavigate to the Teradici PCoIP Graphics Agent installation folder (typically under Program Files or Program Files x86) and verify the presence of NVENC.dllAffected if NVENC.dll exists in the installation directory and the PCoIP Graphics Agent version is below 21.03
-
Verify NVENC.dll file integrityObtain the original hash of NVENC.dll from a known-good installation of version 21.03 or later, then compare it to the hash of the installed file using Get-FileHashAffected if The hash of the installed NVENC.dll does not match the known-good hash from version 21.03 or later, indicating potential replacement
-
Check for unexpected DLL loading locationsUse Sysinternals Process Explorer or process monitor to observe where NVENC.dll is being loaded from at runtimeAffected if NVENC.dll is being loaded from a directory other than the official PCoIP Graphics Agent installation path
The environment is affected if Teradici PCoIP Graphics Agent for Windows is installed at a version lower than 21.03 and the NVENC.dll file shows signs of modification or is loaded from an unauthorized location.
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 data21.03
Upgrade to PCoIP Graphics Agent version 21.03 or later which implements proper DLL validation; alternatively, deploy application whitelisting controls to prevent unauthorized DLL replacement.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-25694 — 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-25694 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