Meraki Gr10 FirmwareOperating system · Cisco
CVE-2020-26141
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 · uneditedAn issue was discovered in the ALFA Windows 10 driver 6.1316.1209 for AWUS036H. The Wi-Fi implementation does not verify the Message Integrity Check (authenticity) of fragmented TKIP frames. An adversary can abuse this to inject and possibly decrypt packets in WPA or WPA2 networks that support the TKIP data-confidentiality protocol.
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 confidenceThe ALFA Windows 10 driver 6.1316.1209 for the AWUS036H Wi-Fi adapter fails to validate the Message Integrity Check (MIC) on fragmented TKIP frames. This allows an attacker within radio range to inject malicious packets into WPA/WPA2 networks using TKIP encryption and potentially decrypt existing traffic.
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
Meraki Gr10 FirmwareOperating system
< 27.7.1
Meraki Gr60 FirmwareOperating system
< 27.7.1
Meraki Mr20 FirmwareOperating system
< 27.7.1
Meraki Mr30h FirmwareOperating system
< 27.7.1
Meraki Mr33 FirmwareOperating system
< 27.7.1
Meraki Mr36 FirmwareOperating system
< 27.7.1
Meraki Mr42 FirmwareOperating system
< 27.7.1
Meraki Mr42e FirmwareOperating system
< 27.7.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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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.
-
Identify your Cisco Meraki modelLocate the model number (Gr10, Gr60, Mr20, Mr30h, Mr33, Mr36, Mr42, or Mr42e) on the device label or in the Meraki dashboard under Access PointsAffected if The device is one of these eight models and is running the vulnerable firmware
-
Check the firmware versionIn the Meraki dashboard, go to Network-wide > Firmware or check the device status page. Compare the installed version number to 27.7.1Affected if The firmware version is lower than 27.7.1 (for example, 27.6.2 or earlier)
-
Verify TKIP encryption is in useIn the Meraki dashboard, go to Wireless > SSIDs > Security. Examine the encryption settings for each SSID. TKIP is typically found under WPA2 Personal or WPA2 Enterprise with TKIP or mixed-mode encryptionAffected if Any SSID is configured to use TKIP encryption (either pure TKIP or WPA/TKIP mixed mode)
You are affected if your device is a Cisco Meraki model Gr10, Gr60, Mr20, Mr30h, Mr33, Mr36, Mr42, or Mr42e running firmware below 27.7.1 AND you have an SSID configured to use TKIP encryption.
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 data27.7.1
Update the ALFA driver to a version that properly validates MIC on fragmented TKIP frames, or migrate to WPA2-AES/WPA3 which are not affected by this vulnerability.
Fix this in Meraki Gr10 Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26141 — 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-2020-26141 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