CVE-2019-14602
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 · uneditedImproper permissions in the installer for the Nuvoton* CIR Driver versions 1.02.1002 and before may allow an authenticated user to potentially enable escalation of privilege via local access.
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 Nuvoton CIR Driver installer versions 1.02.1002 and prior sets improper permissions on files, directories, or registry keys during installation. This allows an authenticated local user to modify service binaries, DLLs, or configuration files that should be protected, enabling privilege escalation to SYSTEM or administrator 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<= 1.02.1002CVSS 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 Nuvoton CIR driver is installedOpen Programs and Features in Control Panel or use 'Get-WmiObject -Class Win32_Product' in PowerShell to list installed software, and look for entries containing 'Nuvoton' or 'Consumer Infrared'Affected if The driver appears in the list of installed programs
-
Check installed versionLocate the Nuvoton CIR driver entry in Programs and Features and note the version number shown, or right-click the driver file in Device Manager and select Properties to view version infoAffected if The version is 1.02.1002 or earlier
-
Inspect driver installation directory permissionsRight-click the driver installation folder in Program Files, select Properties, go to the Security tab, and examine which users and groups have Write or Modify permissionsAffected if Standard users or the 'Users' group have Write or Modify access to the driver directory or its subfolders containing binaries, DLLs, or config files
-
Check service-related registry key permissionsOpen Registry Editor, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\, locate keys related to Nuvoton CIR or CIR service, right-click each key, select Permissions, and review write access for standard usersAffected if Standard users or non-admin groups have Write or Full Control permissions on service registry keys or their subkeys
-
Verify service binary file permissionsLocate the executable(s) used by the Nuvoton CIR service (check the ImagePath value in the service registry key), right-click each binary file, go to Properties > Security, and verify write access is restricted to AdministratorsAffected if Standard users can modify the service binary files
A user is affected if the Nuvoton CIR driver version is 1.02.1002 or earlier AND standard users have Write access to the driver installation directory, service binaries, or related registry keys.
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 when available. In the interim, manually review and restrict permissions on driver installation directories and service-related registry keys to remove write access for standard users.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14602 — 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-14602 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