dbcve.org
Wap371 FirmwareOperating system · Cisco

CVE-2024-20287

HIGH · 7.2 CVSS v3.1 Published 2024-01-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 management interface of the Cisco WAP371 Wireless-AC/N Dual Radio Access Point (AP) with Single Point Setup could allow an authenticated, remote attacker to perform command injection attacks against an affected device. This vulnerability is due to improper validation of user-supplied input. An attacker could exploit this vulnerability by sending crafted HTTP requests to the web-based management interface of an affected system. A successful exploit could allow the attacker to execute arbitrary commands with root privileges on the device. To exploit this vulnerability, the attacker must have valid administrative credentials for the device.

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

Command injection vulnerability in Cisco WAP371 Wireless-AC/N Dual Radio Access Point's web-based management interface. Improper validation of user-supplied input in HTTP requests allows authenticated attackers with administrative credentials to execute arbitrary commands with root privileges on the device.

MitigationApply vendor security patches when available. As an interim control, restrict web management interface access to trusted networks or IP addresses via ACLs, and ensure strong administrative credentials are in use.

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
Wap371 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
High

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

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

  1. Identify the device model
    Access the device web interface or check the physical device label, or use SNMP/CLI to query the device型号. Look for 'WAP371' in the product name or model number.
    Affected if The device is a Cisco WAP371 Wireless-AC/N Dual Radio Access Point
  2. Confirm firmware version
    Log into the web management interface and navigate to Administration > Firmware Upgrade, or use CLI command 'show version' to display the installed firmware version.
    Affected if Any firmware version is installed on the WAP371 device (all versions are affected)
  3. Verify web management interface is enabled
    Check device configuration via CLI using 'show running-config' or through the web interface under Administration > Management. Look for HTTP/HTTPS management service settings.
    Affected if HTTP or HTTPS web management interface is enabled on the device
  4. Check network accessibility of management interface
    Review access control lists (ACLs) or firewall rules that govern which IP addresses or networks can reach the device's web management ports (80/443). Use 'show ip http server status' or 'show ip https server status' in CLI.
    Affected if The web management interface is accessible from untrusted or external networks rather than only from trusted management VLANs
  5. Verify administrative accounts exist
    Check for configured administrative users in the web interface under User Management/Administration > User Accounts, or via CLI command 'show running-config' to view local user accounts.
    Affected if Administrative credentials are configured on the device (required for exploitation, though any valid admin account can be used)

If the device is a Cisco WAP371 with its web management interface enabled and accessible, an attacker with valid administrative credentials could inject and execute arbitrary commands with root privileges.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor security patches when available. As an interim control, restrict web management interface access to trusted networks or IP addresses via ACLs, and ensure strong administrative credentials are in use.

Recommended fix High confidence

Cisco WAP371 fixed firmware release (obtain specific version from Cisco Security Advisory CVE-2024-20287)

  1. 1. Access the Cisco WAP371 web-based management interface using administrative credentials.
  2. 2. Navigate to the Administration or System Settings section to check the current firmware version.
  3. 3. Visit the Cisco Security Advisories page (sec.cloudapps.cisco.com) and search for CVE-2024-20287 to obtain the specific fixed firmware release.
  4. 4. Download the fixed firmware version from the Cisco software download center.
  5. 5. In the web interface, go to Administration > Firmware Upgrade and upload the downloaded fixed firmware file.
  6. 6. Wait for the firmware upload and installation to complete; the device will reboot automatically.
  7. 7. After reboot, verify the firmware version has been updated and test that the device functionality is operational.
  8. 8. Confirm the fix by reviewing the Cisco advisory release notes for this vulnerability.
Caveat Review Cisco release notes for any configuration or feature changes in the fixed firmware before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wap371 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-20287 — 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-20287 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