CVE-2022-41314
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 · uneditedUncontrolled search path in some Intel(R) Network Adapter installer software 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 confidenceThis is an uncontrolled search path vulnerability in Intel Network Adapter installer software. The installer does not use fully qualified paths when loading executables or libraries, allowing an authenticated local attacker to place a malicious executable in a directory that gets searched by the installer, potentially leading to 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< 27.3< 4.01CVSS 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.
-
Check if Intel Administrative Tools is installedLook for the Intel Network Adapter installation directory, typically in Program Files or Program Files (x86)\Intel. Check for executable files like iAP.exe, IntelProAdmin.exe, or similar Intel network adapter management tools.Affected if The software is present on the system and the version is below 27.3
-
Check if Intel Non Volatile Memory Update Utility is installedSearch for the Intel NVMe utility executable, typically in Program Files or Program Files (x86)\Intel\Intel(R) NVMe or similar paths. Look for files named iNVMeUtil.exe or similar.Affected if The software is present on the system and the version is below 4.01
-
Determine installed version of Intel Administrative ToolsRight-click the installed executable, select Properties, then look at the File Version or Product Version field in the Details tab. Alternatively, check the Windows Programs and Features list for the exact version number.Affected if Version shown is less than 27.3
-
Determine installed version of Intel Non Volatile Memory Update UtilityRight-click the installed utility executable, select Properties, then check the File Version or Product Version in the Details tab. Alternatively, check the Windows Programs and Features list for the version.Affected if Version shown is less than 4.01
-
Check for untrusted directories in installer search pathReview the installation directory for the affected software. Look for any unexpected or untrusted executable files (.exe or .dll) in the same folder as the installer or in parent directories that could be pre-loaded.Affected if Any untrusted or suspicious executable files exist in directories that the installer searches during execution
Your environment is affected if either Intel Administrative Tools for Intel Network Adapters below version 27.3 or Intel Non Volatile Memory Update Utility below version 4.01 is installed and the installer can load executables from untrusted directories.
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 · scoped4.0127.3
Apply the vendor patch from Intel to update the Network Adapter installer software to a patched version.
Administrative Tools For Intel Network Adapters: version 27.3 or later; Non Volatile Memory Update Utility: version 4.01 or later
- 1. Identify which affected Intel software is installed on the system (Administrative Tools For Intel Network Adapters and/or Non Volatile Memory Update Utility)
- 2. Uninstall the current version of the affected software via Windows Control Panel > Programs and Features
- 3. Download the updated version from Intel's official support website: search for Intel Network Adapter drivers and tools, and Intel NVMUpdate Utility
- 4. For Administrative Tools For Intel Network Adapters: install version 27.3 or later
- 5. For Non Volatile Memory Update Utility: install version 4.01 or later
- 6. Restart the system after installation to ensure proper initialization
- 7. Verify the installed version matches the fixed release by checking Programs and Features
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41314 — 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-2022-41314 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