dbcve.org
Wap121 FirmwareOperating system · Cisco

CVE-2024-20336

MEDIUM · 6.5 CVSS v3.1 Published 2024-03-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A vulnerability in the web-based user interface of Cisco Small Business 100, 300, and 500 Series Wireless APs could allow an authenticated, remote attacker to perform buffer overflow attacks against an affected device. In order to exploit this vulnerability, the attacker must have valid administrative credentials for the device. This vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability by sending a crafted HTTP request to the web-based management interface of an affected device. A successful exploit could allow the attacker to execute arbitrary code as the root user on the underlying operating system.

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 confidence

Buffer overflow vulnerability in the web-based management interface of Cisco Small Business 100, 300, and 500 Series Wireless APs allows authenticated attackers with admin credentials to send crafted HTTP requests with insufficiently validated user-supplied input, potentially executing arbitrary code as root on the underlying OS.

MitigationApply the vendor-supplied firmware update from Cisco to patch the buffer overflow vulnerability. If no patch is available, restrict web management interface access to trusted networks and enforce strong administrative credential policies to reduce exploitability.

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
Affected:all versions
Wap125 FirmwareOperating system
Affected:all versions
Wap131 FirmwareOperating system
Affected:all versions
Wap150 FirmwareOperating system
Affected:all versions
Wap320 FirmwareOperating system
Affected:all versions
Wap321 FirmwareOperating system
Affected:all versions
Wap351 FirmwareOperating system
Affected:all versions
Wap361 FirmwareOperating system
Affected:all versions

CVSS 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
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the wireless AP model
    Access the device web interface or check the physical device label, or use SNMP or CDP/LLDP to discover the model number. Common paths: https://[device-ip]/ or check the admin console for device information.
    Affected if The model is one of: Wap121, Wap125, Wap131, Wap150, Wap320, Wap321, Wap351, or Wap361.
  2. Verify the web-based management interface is enabled
    Check the device configuration for HTTP or HTTPS management access settings. This is typically found under Administration > Management Access or similar in the web UI. Confirm that web-based management is allowed on at least one interface (LAN or WLAN).
    Affected if Web-based management interface (HTTP/HTTPS) is enabled and accessible.
  3. Confirm admin credentials are in use
    Review the list of configured administrator accounts on the device. Check if the default admin account (admin) still exists with default or weak credentials, or if any admin账户 has a weak/guessable password.
    Affected if An admin account with weak, default, or guessable credentials exists, allowing authenticated attackers to exploit the vulnerability.
  4. Assess network accessibility of the management interface
    Determine if the web management interface is reachable from untrusted networks. Check ACLs, VLANs, or firewall rules that may permit external access to the device management IP on ports 80/443.
    Affected if The web management interface is exposed to untrusted networks or the internet, increasing the likelihood of exploitation.

If the device is one of the affected Wap models (121, 125, 131, 150, 320, 321, 351, 361), the web management interface is enabled, and an attacker could obtain admin credentials, the environment is vulnerable to CVE-2024-20336.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied firmware update from Cisco to patch the buffer overflow vulnerability. If no patch is available, restrict web management interface access to trusted networks and enforce strong administrative credential policies to reduce exploitability.

Fix this in Wap121 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-20336 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-20336 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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