CVE-2021-0058
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 · uneditedIncorrect default permissions in the Intel(R) NUC M15 Laptop Kit Driver Pack software before updated version 1.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 confidenceThis is a local privilege escalation vulnerability in the Intel NUC M15 Laptop Kit Driver Pack where incorrect default file or directory permissions allow an authenticated local user to modify executable files or configuration files that are subsequently run with elevated privileges, enabling privilege escalation from a standard user account.
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.1< 1.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.
-
Confirm Intel NUC M15 modelCheck system information or BIOS to verify the device is an Intel NUC M15 Laptop KitAffected if Device is not an Intel NUC M15, the system is not affected by this specific vulnerability
-
Identify firmware versionAccess BIOS/UEFI settings or use system information tools to determine the installed firmware version for Lapbc510 or Lapbc710Affected if Firmware version is 1.1 or higher, the vulnerability has been patched; if version is below 1.1, the system may be affected
-
Locate driver pack installation directorySearch for Intel NUC driver pack files on the system, typically found in Program Files or System32 directories related to Intel componentsAffected if Driver pack is not installed, this specific vulnerability does not apply
-
Check driver pack file permissionsExamine file and directory permissions on the driver pack files using icacls (Windows) or ls -la (Linux) to determine if standard users have write or modify accessAffected if Standard user accounts can modify executable files or configuration files in the driver pack directory, the vulnerability is present and exploitable
-
Verify executable file ownershipCheck ownership of .exe or .dll files within the driver pack directory to confirm they are not owned by standard usersAffected if Executable files are writable by non-privileged users, privilege escalation is possible
The system is affected if it is an Intel NUC M15 with Lapbc510 or Lapbc710 firmware below version 1.1, and driver pack files are writable by standard users.
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 data1.1
Apply the vendor-provided updated driver pack version 1.1 or later which corrects the default permission settings on affected files and directories.
- Consultation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-0058 — 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-0058 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