CVE-2021-33093
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 · uneditedInsecure inherited permissions in the installer for the Intel(R) NUC M15 Laptop Kit Serial IO driver pack before version 30.100.2104.1 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 confidenceThe Intel NUC M15 Laptop Kit Serial IO driver pack installer before version 30.100.2104.1 contains insecure inherited permissions that allow an authenticated local user to gain elevated privileges. The installer's permission inheritance misconfiguration grants excessive access rights that can be exploited for local 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< 30.100.2104.1CVSS 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 Intel NUC M15 Serial IO Driver Pack is installedOpen Programs and Features (or equivalent) and look for 'Intel NUC M15 Laptop Kit Serial IO Driver Pack' or search for 'Serial IO' in the installed programs listAffected if The program is not found in the installed programs list, then the product is not installed and this CVE does not apply
-
Locate the installed driver pack versionIn Programs and Features, find the Intel NUC M15 Serial IO Driver Pack entry and note the version number displayed in the Version columnAffected if The displayed version number is missing or cannot be determined, further investigation may be required
-
Compare installed version against the vulnerable rangeCompare the installed version to 30.100.2104.1 using standard version number comparison (for example, 30.100.2104.0 would be less than 30.100.2104.1)Affected if The installed version is less than 30.100.2104.1 (for example, 30.100.2102.0 or any 30.100.xxxx version below 30.100.2104.1), the environment is affected by this CVE
The system is affected only if the Intel NUC M15 Serial IO Driver Pack is installed with a version number lower than 30.100.2104.1
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.
dbcve · scoped30.100.2104.1
Update the Intel NUC M15 Serial IO driver pack to version 30.100.2104.1 or later to remediate the insecure permission inheritance issue.
30.100.2104.1 or later
- Identify the current version of the Intel NUC M15 Laptop Kit Serial IO Driver Pack installed on the system
- Navigate to Intel's official support website and download the Serial IO Driver Pack version 30.100.2104.1 or later
- Follow Intel's standard driver installation procedure to apply the updated driver pack
- Restart the system if prompted to complete the installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-33093 — 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-2021-33093 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