CVE-2017-5260
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 · uneditedIn versions 4.3.2-R4 and prior of Cambium Networks cnPilot firmware, although the option to access the configuration file is not available in the normal web administrative console for the 'user' account, the configuration file is accessible via direct object reference (DRO) at http://<device-ip-or-hostname>/goform/down_cfg_file by this otherwise low privilege 'user' account.
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 direct object reference vulnerability in Cambium Networks cnPilot firmware versions 4.3.2-R4 and prior allows authenticated low-privilege 'user' accounts to download the device configuration file via an unprotected endpoint at /goform/down_cfg_file, bypassing the access controls enforced in the normal web administrative console.
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<= 4.3.2-r4<= 4.3.2-r4<= 4.3.2-r4<= 4.3.2-r4<= 4.3.2-r4CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 Cambium cnPilot device modelAccess the device web console or use SNMP/CLI to retrieve the hardware model information. Look for model identifiers: R190v, E410, R190n, E400, or E600.Affected if The device is one of these five models.
-
Check the installed firmware versionNavigate to the device web interface status page or use the CLI command 'show version' to retrieve the firmware version. Compare against 4.3.2-R4.Affected if The firmware version is 4.3.2-R4 or any version prior to it.
-
Verify the vulnerable endpoint existsAttempt to access the URL path /goform/down_cfg_file on the device (e.g., http://device_ip/goform/down_cfg_file). A successful HTTP 200 response with a configuration file download indicates the endpoint is present.Affected if The endpoint responds and triggers a configuration file download without requiring elevated privileges.
-
Confirm low-privilege user account existenceLog into the device web interface using a standard 'user' level account (not admin). Verify that this account type exists and can authenticate.Affected if A low-privilege 'user' account can be created or already exists on the device.
-
Test authorization bypass on the endpointWhile logged in as a low-privilege 'user' account, access /goform/down_cfg_file. If the configuration file downloads without being blocked, the vulnerability is present.Affected if A low-privilege user can download the configuration file through this endpoint.
You are affected if you run any of the five cnPilot models (R190v, E410, R190n, E400, E600) with firmware version 4.3.2-R4 or earlier and the /goform/down_cfg_file endpoint is accessible to low-privilege users.
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 dataUpgrade to a patched firmware version that implements proper authorization checks on the configuration download endpoint. As an interim measure, restrict user account access and monitor for unauthorized configuration file access attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5260 — 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-5260 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