CVE-2019-0164
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 Intel(R) Turbo Boost Max Technology 3.0 driver version 1.0.0.1035 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 confidenceImproper file system or registry permissions in the Intel Turbo Boost Max Technology 3.0 driver installer (versions 1.0.0.1035 and prior) allow an authenticated local user to modify driver-related resources, 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<= 1.0.0.1035all versionsall versionsall versionsall 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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.
-
Locate the Intel Turbo Boost Max Technology 3.0 driver installationSearch the system for files or directories named 'Turbo Boost Max Technology 3.0' or 'itbm' - check common locations such as C:\Program Files\Intel\ and review installed programs listAffected if The driver software is present on the system
-
Determine the installed driver versionRight-click the driver file (typically an .inf or .sys file) and view Properties, or use 'wmic product get name,version' if it shows as installed software, or check the driver file version propertyAffected if The version is 1.0.0.1035 or any version lower (e.g., 1.0.0.1030, 1.0.0.1020)
-
Inspect file system permissions on driver filesRight-click the driver installation folder, go to Properties > Security, and verify which users or groups have Write or Modify permissions - especially check if non-admin users have accessAffected if Authenticated users or standard users have Write, Modify, or Full Control permissions on driver files or folders
-
Check registry permissions for driver-related keysOpen regedit, navigate to HKLM\SYSTEM\CurrentControlSet\Services\ and look for keys related to Turbo Boost Max or ITBM driver, right-click the key, select Permissions, and verify non-admin accounts do not have Full Control or Write accessAffected if Standard users or authenticated users have Full Control or Write permissions on driver service registry keys
A system is affected if the Intel Turbo Boost Max Technology 3.0 driver version 1.0.0.1035 or lower is installed AND either the driver files or associated registry keys grant excessive permissions to non-admin users, allowing potential privilege escalation.
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 dataUpdate the Intel Turbo Boost Max Technology 3.0 driver to a version newer than 1.0.0.1035. If updating is not immediately possible, manually audit and restrict permissions on driver files and associated registry keys to remove excessive user access.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0164 — 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-0164 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