dbcve.org
Epmp 1000 FirmwareOperating system · Cambium Networks

CVE-2017-7922

HIGH · 7.6 CVSS v3.0 Published 2017-06-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable 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
An Improper Privilege Management issue was discovered in Cambium Networks ePMP. The privileges for SNMP community strings are not properly restricted, which may allow an attacker to gain 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 · high confidence

Cambium Networks ePMP devices have improper privilege management for SNMP community strings, allowing unauthorized users to access sensitive information and potentially modify device configurations. The SNMP service does not properly restrict privileges based on community string permissions.

MitigationRestrict SNMP access using access control lists (ACLs), implement SNMPv3 with authentication and encryption, change default community strings to complex unique values, and disable SNMP write access where not required.

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
Epmp 1000 FirmwareOperating system
Affected:all versions
Epmp Elevate FirmwareOperating system
Affected:all versions
Epmp 2000 FirmwareOperating system
Affected:all versions
Epmp 1000 Hotspot FirmwareOperating system
Affected:all versions

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

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

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

  1. Confirm device is a Cambium ePMP model
    Access the device web interface or use SNMP to query the sysDescr OID (1.3.6.1.2.1.1.1.0) to identify the device type and model
    Affected if The device identifies as an ePMP 1000, ePMP Elevate, ePMP 2000, or ePMP 1000 Hotspot model
  2. Verify SNMP is enabled
    Query the device via SNMP using snmpget or snmpwalk on OID 1.3.6.1.4.1.17713.1.7.1 (ePMP SNMP enable status) or check the device web interface under the SNMP configuration section
    Affected if SNMP is enabled and responding to queries
  3. Check for default or weak community strings
    Attempt SNMP queries using default community strings 'public' (read) and 'private' (write) against the device. Compare any configured community strings against known defaults
    Affected if The default community strings 'public' or 'private' are accepted, or any default community strings are in use
  4. Verify SNMP write access configuration
    Use snmpset with a community string to test write access, or inspect the SNMP configuration page in the web interface to see if write access is enabled
    Affected if Write access is granted via the SNMP community string being used
  5. Confirm SNMP access control list status
    Check the SNMP configuration in the web interface or via SNMP OIDs for ACL settings (1.3.6.1.4.1.17713.1.7.x) to see if source IP restrictions are configured
    Affected if No ACL is configured or ACL allows unrestricted SNMP access from any IP
  6. Check SNMP version in use
    Examine device SNMP configuration to determine if SNMPv1, v2c (community-based) or SNMPv3 (user-based) is enabled
    Affected if SNMPv1 or SNMPv2c is in use without SNMPv3 authentication

The device is affected if it is any Cambium ePMP model (1000, Elevate, 2000, or 1000 Hotspot) with SNMP enabled using default community strings, write access enabled, or lacking SNMP access control lists.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict SNMP access using access control lists (ACLs), implement SNMPv3 with authentication and encryption, change default community strings to complex unique values, and disable SNMP write access where not required.

Fix this in Epmp 1000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

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