CVE-2019-12176
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 · uneditedPrivilege escalation in the "HTC Account Service" and "ViveportDesktopService" in HTC VIVEPORT before 1.0.0.36 allows local attackers to escalate privileges to SYSTEM via reconfiguration of either service.
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 confidenceTwo HTC Viveport Windows services (HTC Account Service and ViveportDesktopService) prior to version 1.0.0.36 contain a privilege escalation vulnerability allowing local authenticated users to reconfigure service parameters and execute code as SYSTEM. The services likely have insufficient access controls on their configuration or binary paths, permitting unprivileged users to modify service settings.
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< 1.0.0.36CVSS 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.0/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 HTC Viveport installation statusOpen Programs and Features (appwiz.cpl) or check for HTC Viveport in the installed programs list. Note the installed version if present.Affected if HTC Viveport is installed with a version lower than 1.0.0.36, or the version cannot be determined but the application is present.
-
Identify vulnerable servicesOpen Services console (services.msc) and search for 'HTC Account Service' and 'ViveportDesktopService'. Note whether these services exist on the system.Affected if Either 'HTC Account Service' or 'ViveportDesktopService' is present and the Viveport version is below 1.0.0.36.
-
Retrieve installed Viveport versionCheck the program version through the Programs and Features list, or query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{ViveportInstallID} for the DisplayVersion value, replacing {ViveportInstallID} with the appropriate registry key if present.Affected if The version displayed is lower than 1.0.0.36 (for example, 1.0.0.35, 1.0.0.30, or any version prior to 1.0.0.36).
-
Inspect service binary path permissionsRight-click each affected service in services.msc, select Properties, and examine the 'Path to executable' field. Then right-click the executable file in File Explorer, go to Properties > Security, and verify which users have Write or Modify permissions on the service binary.Affected if Non-privileged users (such as standard users or Authenticated Users) have Write or Modify permissions on the service executable file, allowing them to replace it with a malicious binary.
-
Check service configuration registry permissionsOpen Registry Editor and navigate to HKLM\SYSTEM\CurrentControlSet\Services\<ServiceName> for each affected service (HTC Account Service and ViveportDesktopService). Right-click the service key, select Permissions, and review which users have Full Control, Write, or Modify permissions.Affected if Non-privileged users have Write or Modify permissions on the service registry keys, allowing them to alter the binary path or configuration to execute code as SYSTEM.
A system is affected if HTC Viveport version is below 1.0.0.36 and either the HTC Account Service or ViveportDesktopService is installed with weak permissions allowing unprivileged users to modify service binaries or configuration.
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 data1.0.0.36
Update HTC VIVEPORT to version 1.0.0.36 or later. As a compensating control, verify that service executable files and registry keys have restrictive ACLs limiting modification to Administrators only.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12176 — 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-12176 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