CVE-2019-20362
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 · uneditedIn Teradici PCoIP Agent before 19.08.1 and PCoIP Client before 19.08.3, an unquoted service path can cause execution of %PROGRAMFILES(X86)%\Teradici\PCoIP.exe instead of the intended pcoip_vchan_printing_svc.exe file.
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 confidenceAn unquoted service path vulnerability in Teradici PCoIP Agent before 19.08.1 and PCoIP Client before 19.08.3 causes Windows to attempt executing %PROGRAMFILES(X86)%\Teradici\PCoIP.exe (the first path component with a space) instead of the intended pcoip_vchan_printing_svc.exe service binary, potentially enabling 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.08.1< 19.08.1< 19.08.3CVSS 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.
-
Verify Teradici PCoIP installation existsCheck if the directory %PROGRAMFILES(X86)%\Teradici\ exists or query installed programs via registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Teradici' or 'PCoIP'Affected if The Teradici PCoIP software is installed on the system
-
Identify installed PCoIP component typeList contents of the Teradici folder in Program Files (x86). Look for 'Agent' subfolder (indicating PCoIP Agent) or check for PCoIP Client executable directlyAffected if PCoIP Agent or PCoIP Client is present
-
Determine installed PCoIP versionRight-click the pcoip.exe file in the installation folder, select Properties, then view the Details tab for File Version, or run: wmic product where "name like '%pcoip%'" get versionAffected if The version is less than 19.08.1 for Agent or less than 19.08.3 for Client
-
Check for unquoted service pathRun 'sc qc pcoip_vchan_printing_svc' to query the service configuration. Examine the BINARY_PATH_NAME field. If the path contains spaces and is not enclosed in quotes, it is unquotedAffected if The BINARY_PATH_NAME shows an unquoted path containing spaces (e.g., C:\Program Files (x86)\Teradici\... without quotes)
-
List all PCoIP-related servicesRun 'wmic service where "name like '%pcoip%'" get name,displayname,binarypathname' to see all PCoIP services and their executable pathsAffected if Any PCoIP service shows an unquoted path with spaces in its binary path
A user is affected if Teradici PCoIP Agent version is below 19.08.1 or PCoIP Client version is below 19.08.3 AND any associated Windows service has an unquoted executable path containing spaces.
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 data19.08.119.08.3
Upgrade to PCoIP Agent 19.08.1 or PCoIP Client 19.08.3 or later to implement proper path quoting in the service configuration.
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20362 — 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-2019-20362 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