LiveActive security incident?Get immediate response
CVE Record

CVE-2018-0412: A vulnerability in the implementation of Extensible Authentication Protocol over LAN (EAPOL) functionality...

A 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects Cisco Small Business 100 and 300 Series wireless access points. A nearby attacker who can intercept the Wi-Fi handshake could push a client and access point from stronger AES-CCMP encryption to weaker WPA-TKIP. That downgrade does not itself disclose data, but it can enable later cryptographic attacks against wireless confidentiality.

Executive priority

Treat this as a targeted wireless confidentiality risk, not a broad remote takeover issue. Prioritize if affected access points protect sensitive offices, regulated data, or guest-to-corporate boundary networks. The absence of KEV evidence lowers emergency urgency, but unsupported or unverified firmware should be addressed.

Technical view

Cisco describes improper processing of certain EAPOL messages during the Wi-Fi handshake. In a man-in-the-middle position between supplicant and authenticator, an unauthenticated adjacent attacker could manipulate EAPOL exchange and force TKIP instead of AES-CCMP. The bundle does not provide CVSS details, fixed versions, or observed exploitation evidence.

Likely exposure

Exposure is limited to environments using Cisco Small Business 100 Series or 300 Series Wireless Access Points. The affected version range is unspecified in the provided sources, so teams should verify models, firmware, and Cisco advisory applicability directly.

Exploitation context

The attacker must be adjacent to the wireless network and able to establish a man-in-the-middle position during the Wi-Fi handshake. The sources do not indicate internet-scale exploitation, public exploit use, or CISA KEV listing.

Researcher notes

The key evidence is Cisco's EAPOL downgrade description and Bug ID CSCvj29229. The public bundle lacks CVSS metrics, precise vulnerable firmware ranges, and fixed-release details. Do not assume products outside the named Small Business 100 and 300 Series access points are affected.

Mitigation direction

  • Review Cisco's advisory for affected firmware and vendor-supported remediation.
  • Inventory Cisco Small Business 100 and 300 Series wireless access points.
  • Upgrade or replace affected access points according to Cisco guidance.
  • Where vendor-supported, require AES-CCMP and disable WPA-TKIP.
  • Prioritize higher-risk offices handling sensitive wireless traffic.

Validation and detection

  • Confirm deployed access point models and firmware versions against Cisco's advisory.
  • Review wireless security settings for TKIP allowance or mixed cipher modes.
  • Check whether clients negotiate TKIP where AES-CCMP is expected.
  • Validate that firmware updates or configuration changes preserve normal client connectivity.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-310: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-0412 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Cisco Systems, Inc.Small Business 100 Series Wireless Access PointsunspecifiedListed
Cisco Systems, Inc.Small Business 300 Series Wireless Access PointsunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-310 · source CWE mapping

Cryptographic Issues

Cryptographic Issues represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.