CVE-2019-11155
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 · uneditedImproper directory permissions in Intel(R) PROSet/Wireless WiFi Software before version 21.40 may allow an authenticated user to potentially enable denial of service and information disclosure 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 confidenceIntel PROSet/Wireless WiFi Software versions before 21.40 have improper directory permissions that allow an authenticated local user to access or modify directories they should not have access to, potentially enabling denial of service through disruption of WiFi services or information disclosure of sensitive configuration data.
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< 21.40CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Locate Intel PROSet/Wireless WiFi Software installation directoryCheck common installation paths such as C:\Program Files\Intel\Wireless or C:\Program Files (x86)\Intel\Wireless, or query the Windows registry at HKLM\SOFTWARE\Intel\ProSet\Wireless for the InstallPath value.Affected if The software is installed in a directory accessible to authenticated users.
-
Determine installed version of Intel PROSet/Wireless WiFi SoftwareCheck the file version of the main executable (e.g., WLTRNA.exe or iQUtil.exe) in the installation directory, or view the version in Add/Remove Programs. Alternatively, run 'wmic product where "name like '%Intel%Wireless%'" get name,version' in Command Prompt.Affected if Version is present and is below 21.40.
-
Compare installed version to affected rangeCompare the identified version number to the affected range: any version before 21.40 (e.g., 21.30, 20.x, 19.x) is affected. Versions 21.40 and later are not affected.Affected if Installed version is lower than 21.40.
-
Inspect directory permissions on the Intel WiFi installation folderRight-click the installation directory, select Properties, then Security tab. Verify that only Administrators and SYSTEM have Full Control or Modify permissions. Check if standard authenticated users have excessive access (such as Write or Modify).Affected if Authenticated local users have Write, Modify, or Full Control permissions to the Intel WiFi installation directory.
The system is affected if Intel PROSet/Wireless WiFi Software version below 21.40 is installed AND the installation directory grants excessive permissions to authenticated local 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 data21.40
Upgrade Intel PROSet/Wireless WiFi Software to version 21.40 or later to obtain the corrected directory permissions. Alternatively, manually review and restrict directory permissions on the installation folder to follow least-privilege principles.
- Consultation4.0 h
- Implementation3.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 $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11155 — 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-2019-11155 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