CVE-2017-12281
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 Protected Extensible Authentication Protocol (PEAP) functionality for standalone configurations of Cisco Aironet 1800, 2800, and 3800 Series Access Points could allow an unauthenticated, adjacent attacker to bypass authentication and connect to an affected device. The vulnerability exists because the affected device uses an incorrect default configuration setting of fail open when running in standalone mode. An attacker could exploit this vulnerability by attempting to connect to an affected device. A successful exploit could allow the attacker to bypass authentication and connect to the affected device. This vulnerability affects Cisco Aironet 1800, 2800, and 3800 Series Access Points that are running a vulnerable software release and use WLAN configuration settings that include FlexConnect local switching and central authentication with MAC filtering. Cisco Bug IDs: CSCvd46314.
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 PEAP implementation for Cisco Aironet 1800, 2800, and 3800 Series Access Points running in standalone mode allows unauthenticated adjacent attackers to bypass authentication. The root cause is an incorrect default 'fail open' configuration setting instead of 'fail closed', which permits connections when authentication should fail. This affects devices using WLAN configurations with FlexConnect local switching and central authentication with MAC filtering.
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 dataall versionsall versionsall versionsCVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/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.
-
Identify the access point modelCheck the device model through the Cisco Aironet web interface, CLI (show version), or SNMP inventory. Look for model numbers 1800, 2800, or 3800 series.Affected if The device is a Cisco Aironet 1800, 2800, or 3800 series access point.
-
Verify standalone mode operationCheck the access point configuration through CLI (show controllers) or the web interface to confirm it is running in standalone (autonomous) mode rather than lightweight mode (joined to a WLC).Affected if The access point is operating in standalone (autonomous) mode.
-
Confirm FlexConnect local switching is enabledExamine the WLAN configuration through the web interface (Wireless > WLANs > Edit) or CLI (show wlan) to determine if FlexConnect local switching is enabled for the affected WLANs.Affected if FlexConnect local switching is enabled on the WLAN configuration.
-
Verify central authentication with MAC filteringReview the WLAN security settings to confirm that central authentication is configured (typically with a RADIUS server) and that MAC filtering is enabled as an additional authentication method.Affected if The WLAN uses central authentication with MAC filtering enabled.
-
Check authentication fail-open settingInspect the WLAN security configuration for the authentication fail-open/fail-closed setting. In the web interface, this is found under Wireless > WLANs > Security > Layer 2 > Authentication Fail Tolerance or similar. In CLI, use show wlan to display the authentication parameters.Affected if The authentication fail-open setting is set to 'fail open' (allowing connections when authentication fails) instead of 'fail closed'.
A user is affected if they have a Cisco Aironet 1800, 2800, or 3800 series AP in standalone mode with FlexConnect local switching and central authentication using MAC filtering, where the authentication fail-open setting is configured to allow connections on authentication failure.
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 dataChange the default authentication fail-open setting to fail-closed in the WLAN configuration for affected access points. Verify that wireless clients are properly authenticated before granting network access.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12281 — 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-2017-12281 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