CVE-2018-3634
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 · uneditedParameter corruption in NDIS filter driver in Intel Online Connect Access 1.9.22.0 allows an attacker to cause a denial of service 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 parameter corruption vulnerability exists in the NDIS filter driver component of Intel Online Connect Access 1.9.22.0. The flaw allows a local attacker to corrupt parameters within the network driver, leading to a denial of service condition.
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.9.22.0CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 Intel Online Connect Access versionOpen Windows Control Panel > Programs and Features, or run 'wmic product get name,version' to list installed Intel software. Look for 'Intel Online Connect Access' and note the version number displayed.Affected if The version is 1.9.22.0 or any version lower (e.g., 1.9.20.0, 1.9.0.0, etc.)
-
Verify NDIS filter driver presenceOpen Device Manager, expand 'Network adapters' and look for any Intel network filter drivers related to Online Connect. Alternatively, run 'netsh wfp show state' to list active NDIS filter drivers loaded in the system.Affected if An Intel Online Connect NDIS filter driver is present and loaded in the network stack
-
Check for driver file detailsLocate the NDIS filter driver file. Common paths include C:\Program Files\Intel\ or C:\Windows\System32\drivers\. Look for files with 'NdisFlt', 'Ndis', or 'OnlineConnect' in the filename. Right-click > Properties to view version info.Affected if The driver file version is 1.9.22.0 or lower, matching the vulnerable software version range
A user is affected if Intel Online Connect Access version 1.9.22.0 or lower is installed and its NDIS filter driver component is present and loaded on the system.
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 dataUpdate Intel Online Connect Access to a patched version once available, or consider removing the software if unused, as the vulnerability is exploitable via local access and could disrupt network functionality.
- 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-2018-3634 — 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-2018-3634 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