dbcve.org
Nuc M15 Laptop Kit Integrated Sensor Hub Driver PackOperating system · Intel

CVE-2021-33088

HIGH · 7.8 CVSS v3.1 Published 2021-11-17
Fix available
A fix is available. Upgrade to 5.4.1.4449 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Incorrect default permissions in the installer for the Intel(R) NUC M15 Laptop Kit Integrated Sensor Hub driver pack before version 5.4.1.4449 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 confidence

The installer for the Intel NUC M15 Laptop Kit Integrated Sensor Hub driver pack (versions before 5.4.1.4449) sets incorrect default permissions on installed files, allowing an authenticated local user to modify privileged resources and potentially escalate their privileges.

MitigationUpdate the Intel NUC M15 Laptop Kit Integrated Sensor Hub driver pack to version 5.4.1.4449 or later to remediate the incorrect permission issue in the installer.

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
Nuc M15 Laptop Kit Integrated Sensor Hub Driver PackOperating system
Affected:< 5.4.1.4449

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Intel NUC M15 Laptop Kit ISH Driver Pack is installed
    Open Windows Settings > Apps & Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, and search for entries containing 'Intel NUC M15' and 'Integrated Sensor Hub' or 'ISH Driver'
    Affected if The product appears in the installed programs list
  2. Identify installed version of the driver pack
    Right-click the installed program in Apps & Features and select 'Advanced' or check the driver file properties in the installation directory. You can also check version info using 'Get-ItemProperty' on the driver DLL or exe files in the installation folder
    Affected if The version number displayed is less than 5.4.1.4449 or cannot be determined (missing version info)
  3. Locate the driver pack installation directory
    Check typical driver installation paths such as C:\Program Files\Intel\ or C:\ProgramData\Intel\, or right-click the installed application and select 'Open file location'
    Affected if Files are found in Intel driver directories for the NUC M15 Laptop Kit
  4. Inspect file permissions on the installed driver files
    Right-click the driver files in the installation folder, select Properties > Security tab, and verify which users and groups have Write or Modify permissions. Alternatively, use 'icacls <filename>' in Command Prompt to view effective permissions
    Affected if Authenticated standard users have Write or Modify permissions on driver files that should be restricted to Administrators only

The environment is affected if the Intel NUC M15 Laptop Kit Integrated Sensor Hub Driver Pack is installed with a version prior to 5.4.1.4449 and standard users have elevated write permissions on the driver files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 5.4.1.4449 or later
Fixed in 5.4.1.4449
Interim mitigation

Update the Intel NUC M15 Laptop Kit Integrated Sensor Hub driver pack to version 5.4.1.4449 or later to remediate the incorrect permission issue in the installer.

Recommended fix High confidence

5.4.1.4449

  1. Identify the current version of Intel NUC M15 Laptop Kit Integrated Sensor Hub Driver Pack installed on the system via Device Manager or Intel Driver & Support Assistant
  2. Download the updated driver pack version 5.4.1.4449 or later from Intel's official support website (intel.com)
  3. Uninstall the current version of the Integrated Sensor Hub driver pack through Windows Control Panel > Programs and Features or via Device Manager
  4. Restart the system if prompted during uninstallation
  5. Run the installer for version 5.4.1.4449 with administrator privileges
  6. Follow the on-screen installation wizard prompts to complete the installation
  7. Restart the system after installation completes successfully
  8. Verify the installed version is 5.4.1.4449 or later via Device Manager or Intel utility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nuc M15 Laptop Kit Integrated Sensor Hub Driver Pack Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-33088 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-33088 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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