CVE-2017-5254
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 version 3.5 and prior of Cambium Networks ePMP firmware, the non-administrative users 'installer' and 'home' have the capability of changing passwords for other accounts, including admin, after disabling a client-side protection mechanism.
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 confidenceIn Cambium Networks ePMP firmware versions 3.5 and prior, low-privilege users with 'installer' or 'home' roles can change passwords for any account, including the admin account, by bypassing a client-side protection mechanism. This constitutes a privilege escalation vulnerability where unauthenticated or low-authorization users can gain full administrative control over the device.
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<= 3.5<= 3.5CVSS 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 ePMP device model and firmware versionAccess the device web interface or use SNMP to query the firmware version. Look for the firmware version displayed on the device status page or in the system information section.Affected if The device is an ePMP 1000 or ePMP 2000 running firmware version 3.5 or lower.
-
Confirm the exact firmware version numberNavigate to the device administration interface and locate the firmware version information, typically found under Status, Device Info, or System Summary pages.Affected if The displayed firmware version is 3.5 or any version number lower than 3.5 (such as 3.4.x, 3.3.x, etc.).
-
Identify existing user accounts and their rolesAccess the user management or accounts section of the web interface. Review the list of configured users and note their assigned roles (admin, installer, home).Affected if Any user account is assigned the 'installer' or 'home' role, indicating low-privilege accounts exist on the device.
-
Verify management interface accessibilityDetermine if the device web management interface is reachable from untrusted networks. Check networkACLs, firewall rules, or VLAN configurations that control access to the device IP address.Affected if The management interface is accessible from networks outside the trusted administrative network, allowing potential attackers to reach the login page.
You are affected if your ePMP 1000 or ePMP 2000 device runs firmware version 3.5 or lower and has low-privilege accounts (installer or home roles) with access to the management interface.
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 ePMP firmware to version 3.5.1 or later. Until patched, disable or closely monitor low-privilege accounts and restrict device management interface access to trusted networks.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5254 — 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-5254 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