dbcve.org
Cnpilot R200 Series FirmwareOperating system · Cambiumnetworks

CVE-2017-5859

CRITICAL · 9.8 CVSS v3.1 Published 2017-03-10
Fix available
A fix is available. Upgrade to after 4.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
On Cambium Networks cnPilot R200/201 devices before 4.3, there is a vulnerability involving the certificate of the device and its RSA keys, aka RBN-183.

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 · low confidence

The vulnerability affects Cambium Networks cnPilot R200/201 devices prior to firmware version 4.3 and involves issues with the device certificate and RSA cryptographic keys. The CVSS score of 9.8 indicates critical severity, likely suggesting weak or compromised cryptographic implementation that could enable remote unauthenticated attackers to intercept communications or impersonate devices.

MitigationUpgrade cnPilot R200/201 devices to firmware version 4.3 or later. If immediate patching is not possible, restrict network exposure of management interfaces and monitor for suspicious SSL/TLS connections.

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
Cnpilot R200 Series FirmwareOperating system
Affected:<= 4.2

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Identify device model and firmware version
    Access the cnPilot device web interface or CLI and navigate to System > Status or use the 'show version' command via SSH/Telnet to retrieve the firmware version number
    Affected if The firmware version is 4.2 or earlier, or if the version cannot be determined and the device is a cnPilot R200 or R201 model
  2. Inspect SSL/TLS certificate configuration
    Access the device management interface and navigate to System > Certificates or SSL Settings to view the currently loaded device certificate
    Affected if The device uses a default, factory-installed certificate or a certificate with known weak RSA key parameters (e.g., keys smaller than 2048 bits)
  3. Verify management interface exposure
    Check network configuration to determine if the cnPilot web management interface (HTTPS port 443) or CLI (SSH/Telnet) is accessible from untrusted networks or the public internet
    Affected if The management interface is directly exposed to untrusted networks without VPN, firewall, or ACL restrictions

The device is affected if it is a cnPilot R200 or R201 running firmware version 4.2 or earlier, particularly if weak or default certificates are in use and the management interface is network-accessible.

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
Upgrade available Upgrade to a release after 4.2
Interim mitigation

Upgrade cnPilot R200/201 devices to firmware version 4.3 or later. If immediate patching is not possible, restrict network exposure of management interfaces and monitor for suspicious SSL/TLS connections.

Recommended fix Moderate confidence

Firmware version 4.3 or later

  1. 1. Backup the current device configuration before proceeding with firmware upgrade
  2. 2. Download the firmware version 4.3 or later from Cambium Networks support portal (support.cambiumnetworks.com)
  3. 3. Access the cnPilot R200/R201 web management interface
  4. 4. Navigate to the firmware upgrade section (typically under System or Maintenance)
  5. 5. Upload the downloaded firmware file (.bin)
  6. 6. Wait for the upload to complete and for the device to reboot
  7. 7. Verify the firmware version has been updated to 4.3 or later
  8. 8. Restore the configuration if a backup was restored

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

Fix this in Cnpilot R200 Series Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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 locally
dbcve dependency scanner

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