CVE-2022-27808
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 · uneditedInsufficient control flow management in some Intel(R) Ethernet Controller Administrative Tools drivers for Windows before version 1.5.0.2 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 confidenceA vulnerability in Intel Ethernet Controller Administrative Tools drivers for Windows (versions before 1.5.0.2) allows an authenticated local user to escalate privileges due to insufficient control flow management in the driver. The flaw permits a local attacker to gain elevated system privileges.
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.6CVSS 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 Ethernet Controller Administrative Tools is installedOpen Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, and look for entries containing 'Intel Administrative Tools', 'Intel Ethernet', or similar Intel network adapter management software.Affected if The software is listed in installed programs and the version is below 27.6 (or the driver version is below 1.5.0.2).
-
Identify the installed version numberRight-click the Intel Administrative Tools entry in Programs and Features and select 'Change' or 'Properties', or locate the driver file (typically in C:\Program Files\Intel\ or C:\Windows\System32\drivers\) and view its version via right-click > Properties > Details.Affected if The version shown is earlier than 27.6, or the driver file version is earlier than 1.5.0.2.
-
Confirm driver file version via command lineOpen Command Prompt or PowerShell and run 'driverquery /v | findstr -i intel' or check specific driver files such as 'fta*.sys' or 'e1d*.sys' in System32\drivers using 'driverquery /fo list' and review the Module Name and Version columns.Affected if An Intel network driver file version is reported as lower than 1.5.0.2.
-
Check registry for version informationRun 'reg query "HKLM\SOFTWARE\Intel\"' or check under 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall' for keys containing 'Intel' and 'Administrative Tools', then review the 'DisplayVersion' value.Affected if The registry displays a version number less than 27.6 or less than 1.5.0.2 for the relevant component.
A user is affected if Intel Ethernet Controller Administrative Tools or its associated driver is installed with a version number below 27.6 (or driver version below 1.5.0.2), allowing a local authenticated attacker to potentially escalate privileges.
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 · scoped27.6
Update Intel Ethernet Controller Administrative Tools to version 1.5.0.2 or later. Apply the vendor patch through standard Windows update mechanisms or manual driver installation after testing.
Administrative Tools for Intel Network Adapters version 1.5.0.2 or later
- Navigate to the Intel support website and locate the Administrative Tools for Intel Network Adapters download page
- Download version 1.5.0.2 or later of the Administrative Tools for Intel Network Adapters for Windows
- Run the installer with administrator privileges
- Follow the on-screen installation prompts
- Restart the system if prompted to complete the installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27808 — 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-27808 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