CVE-2019-0129
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 for Intel(R) USB 3.0 Creator Utility all versions 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 · moderate confidenceLocal privilege escalation vulnerability in Intel(R) USB 3.0 Creator Utility due to improper permission controls. An authenticated local user could exploit misconfigured permissions to gain elevated system 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 dataall versionsCVSS 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.
-
Check if Intel USB 3.0 Creator Utility is installedLook for the utility in the Windows Start Menu, check Program Files folders (C:\Program Files\Intel\ or C:\Program Files (x86)\Intel\), or use Programs and Features in Control PanelAffected if The utility is present on the system
-
Locate the main executableSearch for files named 'USB 3.0 Creator' or similar in Program Files directories, common path is C:\Program Files\Intel\USB 3.0 Creator\Affected if The executable file exists on the system
-
Inspect file permissions on the utility folder and executableRight-click the folder or executable, select Properties, go to the Security tab. Check which users/groups have Write or Modify permissions. From command line: icacls "C:\Program Files\Intel\USB 3.0 Creator"Affected if Authenticated users or non-admin users have Write, Modify, or Full Control permissions to the utility folder or its executable
-
Verify service configuration if installed as a Windows serviceOpen Services (services.msc), look for Intel USB 3.0 Creator service. Check the executable path in service properties and examine permissions on that binaryAffected if The service binary is writable by standard users or the service runs with elevated privileges and has weak file permissions
-
Check for unauthorized or modified executableCompare file hashes of the utility executable against a known-good baseline if available, or verify the executable has not been replaced/modified by checking file properties (signatures, version info)Affected if The executable has been modified or replaced, or digital signatures are missing/invalid
If Intel USB 3.0 Creator Utility is installed and standard users have Write or Modify permissions on its folder or executable, the system is vulnerable to local privilege escalation via this CVE.
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 vendor patches or updates for Intel USB 3.0 Creator Utility when available; if no patch exists, restrict user access to the utility or uninstall if not required.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0129 — 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-0129 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