CVE-2017-7918
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 · uneditedAn Improper Access Control issue was discovered in Cambium Networks ePMP. After a valid user has used SNMP configuration export, an attacker is able to remotely trigger device configuration backups using specific MIBs. These backups lack proper access control and may allow access to sensitive information and possibly allow for configuration changes.
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 · moderate confidenceImproper access control in Cambium Networks ePMP allows unauthenticated remote triggering of configuration backups via specific SNMP MIBs after a legitimate user has performed an SNMP configuration export. The backups lack access controls and expose sensitive device configuration information.
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 dataall versionsall versionsall versionsall versionsCVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:L
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 Cambium ePMP deviceDetermine if the target device is a Cambium Networks ePMP model (1000, 2000, Elevate, or 1000 Hotspot) by checking the device web interface, SNMP sysDescr OID (1.3.6.1.2.1.1.1), or via SNMP GET on .1.3.6.1.2.1.1.2 for the enterprise OIDAffected if The device is a Cambium ePMP 1000, 2000, Elevate, or 1000 Hotspot model
-
Verify SNMP is enabledCheck the device SNMP configuration via the web management interface under the SNMP section, or query SNMP for snmpEnableAuthenTraps (1.3.6.1.2.1.11.30) or other SNMP status OIDsAffected if SNMP is enabled and running on the device
-
Confirm SNMP access from untrusted sourcesReview SNMP access control lists or firewall rules to determine if SNMP UDP port 161 is reachable from IP addresses outside the trusted management networkAffected if SNMP is accessible from untrusted or management IP addresses
-
Check for SNMP configuration export activityReview device logs or syslog for entries indicating SNMP configuration export operations, specifically look for SNMP MIB access patterns related to configuration backup triggersAffected if SNMP configuration export has been performed and MIB access logs exist showing the backup trigger operation
-
Inspect for exposed configuration backup filesCheck the device file system or remote backup locations for configuration backup files that may have been created via unauthenticated SNMP-triggered exports. Verify file access permissions on any stored backupsAffected if Configuration backup files exist and lack proper access controls, or were created without authentication following an authorized export
A user is affected if they have a Cambium ePMP device with SNMP enabled and accessible from untrusted networks, where an unauthorized party could trigger configuration backups via specific SNMP MIBs after a legitimate SNMP configuration export has occurred.
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 dataRestrict SNMP access to trusted management IPs only, disable SNMP if not required, or apply vendor firmware updates if available. Monitor for unauthorized SNMP MIB access attempts.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2017-7918 — 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-7918 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