Wap121 FirmwareOperating system · Cisco
CVE-2018-0412
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 · uneditedA vulnerability in the implementation of Extensible Authentication Protocol over LAN (EAPOL) functionality in Cisco Small Business 100 Series Wireless Access Points and Cisco Small Business 300 Series Wireless Access Points could allow an unauthenticated, adjacent attacker to force the downgrade of the encryption algorithm that is used between an authenticator (access point) and a supplicant (Wi-Fi client). The vulnerability is due to the improper processing of certain EAPOL messages that are received during the Wi-Fi handshake process. An attacker could exploit this vulnerability by establishing a man-in-the-middle position between a supplicant and an authenticator and manipulating an EAPOL message exchange to force usage of a WPA-TKIP cipher instead of the more secure AES-CCMP cipher. A successful exploit could allow the attacker to conduct subsequent cryptographic attacks, which could lead to the disclosure of confidential information. Cisco Bug IDs: CSCvj29229.
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 confidenceA vulnerability in the EAPOL implementation in Cisco Small Business 100/300 Series Wireless Access Points allows an unauthenticated adjacent attacker with MITM positioning to manipulate EAPOL messages during Wi-Fi handshake, forcing downgrade from secure AES-CCMP to weaker WPA-TKIP cipher, enabling subsequent cryptographic attacks and disclosure of confidential information.
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
Wap121 FirmwareOperating system
<= 1.0.6.6
Wap125 FirmwareOperating system
<= 1.0.6.6
Wap131 FirmwareOperating system
<= 1.0.6.6
Wap150 FirmwareOperating system
<= 1.0.6.6
Wap321 FirmwareOperating system
<= 1.0.6.6
Wap351 FirmwareOperating system
<= 1.0.6.6
Wap361 FirmwareOperating system
<= 1.0.6.6
Wap371 FirmwareOperating system
<= 1.0.6.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
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:A/AC:H/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 the Cisco WAP modelLocate the device model number on the physical unit label or access the web GUI to view System Information under the Administration menuAffected if The model is one of Wap121, Wap125, Wap131, Wap150, Wap321, Wap351, Wap361, or Wap371
-
Check the installed firmware versionIn the web GUI go to Administration > System Information and locate the Firmware Version field, or use the CLI command "show version"Affected if The firmware version is 1.0.6.6 or lower
-
Verify wireless security cipher configurationIn the web GUI navigate to Wireless > Security and inspect the WPA Cipher settings; verify whether TKIP is enabled or if only AES-CCMP is selectedAffected if TKIP or TKIP+AES-CCMP cipher is enabled, allowing WPA-TKIP as a fallback
-
Confirm Wi-Fi accessibilityVerify that the wireless interface is enabled and accessible to adjacent attackers by checking the Radio Status under Wireless > Radio settingsAffected if The wireless radio is enabled and broadcasting, permitting adjacent attackers to position themselves for MITM attacks
You are affected if you run any of the listed WAP models with firmware version 1.0.6.6 or lower and have TKIP cipher enabled in your wireless security configuration, combined with an enabled and accessible wireless interface.
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 dataApply Cisco firmware updates addressing CSCvj29229 and configure access points to disable TKIP and enforce AES-CCMP encryption only.
Fix this in Wap121 Firmware
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0412 — 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-0412 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