CVE-2020-13173
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 · uneditedInitialization of the pcoip_credential_provider in Teradici PCoIP Standard Agent for Windows and PCoIP Graphics Agent for Windows versions 19.11.1 and earlier creates an insecure named pipe, which allows an attacker to intercept sensitive information or possibly elevate privileges via pre-installing an application which acquires that named pipe.
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 confidenceThe pcoip_credential_provider component in Teradici PCoIP agents creates a named pipe during initialization with insecure permissions, allowing any local user or pre-installed malicious application to connect to it. An attacker can intercept sensitive credential information transmitted through this pipe or potentially execute code in the security context of the credential provider for privilege escalation.
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<= 19.11.1<= 19.11.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
- 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.
-
Identify if Teradici PCoIP agent is installedLook for PCoIP agent software on the system. On Windows, check Programs and Features or the installation directory (commonly C:\Program Files\Teradici). On Linux, check package manager listings for pcoip-agent packages.Affected if Either the PCoIP Graphics Agent or PCoIP Standard Agent is present on the system
-
Check the installed PCoIP agent versionLocate the version information for the installed PCoIP agent. On Windows, right-click the agent executable in Program Files\Teradici and view Properties > Details, or check Add/Remove Programs. On Linux, run rpm -qa | grep pcoip or dpkg -l | grep pcoip.Affected if The installed version is 19.11.1 or any earlier version (19.x.y where y < 1, or any 18.x or earlier version)
-
Verify pcoip_credential_provider component existsCheck if the pcoip_credential_provider service or executable is present on the system. On Windows, look in the Teradici installation directory for pcoip_credential_provider.exe or check Services for a related service entry.Affected if The pcoip_credential_provider component is installed and present on the system
-
Inspect named pipe permissionsUse operating system tools to examine the security descriptor of any pcoip_credential_provider named pipe. On Windows, use PowerShell Get-Acl or pipelist.exe to list pipe handles, then check if all users have connect access.Affected if The named pipe grants excessive permissions allowing any local user to connect (rather than restricting to SYSTEM or privileged accounts)
A system is affected if it runs Teradici PCoIP Graphics Agent or Standard Agent version 19.11.1 or earlier, with the pcoip_credential_provider component present and the named pipe accessible to all local users.
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 dataApply the vendor patch for versions 19.11.1 and earlier. If patching is not immediately possible, restrict local user permissions and monitor for unauthorized processes attempting to access the pcoip_credential_provider pipe.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13173 — 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-2020-13173 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