CVE-2017-5257
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, an attacker who knows (or guesses) the SNMP read/write (RW) community string can insert XSS strings in certain SNMP OIDs which will execute in the context of the currently-logged on user.
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 confidenceThis is a stored XSS vulnerability in Cambium Networks ePMP firmware 3.5 and prior. An attacker with knowledge of the SNMP read/write community string can inject malicious JavaScript into specific SNMP OIDs. When an administrator views these OIDs in the web management interface, the XSS payload executes in the context of the logged-in user's session.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the web management interface or check the device label to confirm it is a Cambium ePMP 1000 or ePMP 2000 access point.Affected if The device is not an ePMP 1000 or ePMP 2000, the vulnerability does not apply.
-
Check the installed firmware versionLog into the web management interface and navigate to the Status or Device Information page to view the firmware version, or use SNMP to query the device sysDescr OID.Affected if The firmware version is 3.5 or lower.
-
Verify if SNMP is enabledCheck the SNMP configuration page in the web management interface, or attempt an SNMP walk using the community string.Affected if SNMP is enabled with write access.
-
Determine if SNMP write community is defaultReview the SNMP community string configuration. Default read/write communities for ePMP devices are typically 'public' (read) and 'private' (write).Affected if The SNMP write community string is set to the default 'private' or is otherwise easily guessable.
-
Confirm admin access to SNMP OIDs in web UILog in as an administrator and navigate to the SNMP settings or monitoring pages where SNMP OID values are displayed.Affected if An administrator can view SNMP OID values through the web interface, which is the trigger condition for the XSS.
You are affected if you are running Cambium ePMP 1000 or 2000 firmware version 3.5 or lower with SNMP enabled and a known/guessable write community string, and administrators view SNMP OIDs in the web 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 dataImmediately change default SNMP community strings from defaults, update firmware to a version beyond 3.5, and restrict SNMP access to trusted management networks via ACLs.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5257 — 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-5257 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