CVE-2019-17066
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 Ivanti WorkSpace Control before 10.4.40.0, a user can elevate rights on the system by hijacking certain user registries. This is possible because pwrgrid.exe first checks the Current User registry hives (HKCU) when starting an application with elevated rights.
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 confidenceIn Ivanti WorkSpace Control before 10.4.40.0, the pwrgrid.exe component checks Current User (HKCU) registry hives before Local Machine (HKLM) hives when launching applications with elevated privileges. This allows a local authenticated attacker to manipulate HKCU registry keys to hijack the elevated application execution flow and gain higher privileges.
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< 10.4.40.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
- 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.
-
Check Ivanti Workspace Control versionOpen Windows Registry and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or look for Ivanti Workspace Control in Programs and Features to find the installed version numberAffected if The installed version is below 10.4.40.0
-
Locate pwrgrid.exe componentSearch for pwrgrid.exe in the Ivanti Workspace Control installation directory (commonly in C:\Program Files\Ivanti\Workspace Control or similar)Affected if pwrgrid.exe exists and the version is vulnerable
-
Check HKCU registry for application launch keysInspect registry keys under HKCU\SOFTWARE\ that relate to application launching or execution paths controlled by Ivanti Workspace ControlAffected if Non-administrative users have write access to registry keys that influence elevated application execution
-
Verify HKCU takes precedence over HKLMReview the application configuration or documentation for Ivanti Workspace Control to confirm registry hive precedence settings for elevated app launchesAffected if HKCU is configured to be checked before HKLM for elevated application launching
The environment is affected if Ivanti Workspace Control version is below 10.4.40.0 and pwrgrid.exe is present with HKCU registry keys writable by local users for elevated application execution flow.
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 data10.4.40.0
Upgrade Ivanti WorkSpace Control to version 10.4.40.0 or later. As a compensating control, restrict local user write access to the affected registry keys and monitor for unauthorized modifications.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17066 — 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-17066 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