Business 150ax FirmwareOperating system · Cisco
CVE-2023-20112
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 Cisco access point (AP) software could allow an unauthenticated, adjacent attacker to cause a denial of service (DoS) condition on an affected device. This vulnerability is due to insufficient validation of certain parameters within 802.11 frames. An attacker could exploit this vulnerability by sending a wireless 802.11 association request frame with crafted parameters to an affected device. A successful exploit could allow the attacker to cause an unexpected reload of an affected device, resulting in a DoS condition.
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 Cisco access point software allows an unauthenticated, adjacent attacker to cause denial of service by sending malformed 802.11 association request frames with crafted parameters. The insufficient validation of these parameters triggers an unexpected device reload, resulting in service disruption.
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
Business 150ax FirmwareOperating system
< 10.3.2.0
Business 151axm FirmwareOperating system
< 10.3.2.0
Catalyst 9105ax FirmwareOperating system
< 10.3.2.0
Catalyst 9105axi FirmwareOperating system
< 10.3.2.0
Catalyst 9105axw FirmwareOperating system
< 10.3.2.0
Catalyst 9105i FirmwareOperating system
< 10.3.2.0
Catalyst 9105w FirmwareOperating system
< 10.3.2.0
Catalyst 9115 FirmwareOperating system
< 10.3.2.0CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Identify the Cisco access point modelLog into the access point CLI via SSH or console, or check the web interface to confirm the exact model number (e.g., Catalyst 9105ax, Business 150ax)Affected if The model is any of: Cisco Business 150ax, 151axm, Catalyst 9105ax, 9105axi, 9105axw, 9105i, 9105w, or 9115
-
Determine the installed firmware versionExecute the command 'show version' in the AP CLI, or navigate to the Administration > Firmware Upgrade section in the web interface to view the current firmware versionAffected if The firmware version displayed is lower than 10.3.2.0
-
Verify the wireless radio is enabledCheck the wireless configuration via 'show wireless summary' or 'show run-config' in the CLI, or confirm the SSID is active in the web interface under Wireless > SSIDsAffected if The access point has an active SSID and wireless radios are enabled (the vulnerability triggers via 802.11 association requests, so the radio must be up)
You are affected if your Cisco AP model matches one of the listed products AND your installed firmware version is below 10.3.2.0 AND the wireless radio is enabled to accept association requests.
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.
dbcve · scoped10.3.2.0
Apply the vendor-provided security patch for Cisco access point software to address the insufficient input validation vulnerability.
10.3.2.0 or later
- 1. Identify the specific access point model from the affected product list
- 2. Download the appropriate firmware version 10.3.2.0 or later from Cisco's official software download center
- 3. Verify the integrity of the firmware file using checksums provided by Cisco
- 4. Access the access point's web interface or CLI management console
- 5. Navigate to the firmware upgrade section (typically under Administration > Firmware Upgrade or similar
- 6. Upload and apply the firmware version 10.3.2.0 or later
- 7. Allow the device to complete the upgrade process and automatically reboot
- 8. Verify the new firmware version is installed correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Business 150ax Firmware
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20112 — 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-2023-20112 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