CVE-2014-4862
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 · uneditedThe Netmaster CBW700N cable modem with software 81.447.392110.729.024 has an SNMP community of public, which allows remote attackers to obtain sensitive credential, key, and SSID information via an SNMP request.
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 confidenceThe Netmaster CBW700N cable modem ships with a hardcoded SNMP community string of 'public', allowing unauthenticated remote attackers to query the device and retrieve sensitive information including administrative credentials, encryption keys, and wireless SSIDs via SNMP requests.
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= 81.447.392110.729.024all 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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 Netmaster CBW700N or CBW700 devices on your networkScan your network IP range and query SNMP on discovered devices to identify the vendor and model. Use commands like 'snmpwalk -v2c -c public <IP> system' or network scanning tools that can identify device fingerprints.Affected if A device responds to SNMP queries and identifies as Netmaster CBW700N (any version) or Netmaster CBW700 (version 81.447.392110.729.024)
-
Verify if SNMP community string 'public' is activeSend an SNMP GET request using community string 'public' to the target device. For example: snmpget -v2c -c public <IP> sysDescr.0Affected if The device accepts 'public' as the community string and returns valid SNMP responses without authentication failure
-
Check if sensitive OIDs return administrative credentials or keysQuery common SNMP OIDs that may expose sensitive data such as SNMPv2-MIB::sysDescr.0, or vendor-specific OIDs for user accounts and encryption keys using 'snmpwalk -v2c -c public <IP>'Affected if The SNMP query returns administrative credentials, encryption keys, wireless SSIDs, or other sensitive configuration data that should not be publicly accessible
-
Confirm the device firmware version matches affected rangeQuery SNMP OID for firmware version or access the device web interface to check the software version displayed in the status or about pageAffected if The device firmware version equals 81.447.392110.729.024 (CBW700) or is an unknown version on a CBW700N model, confirming it falls within the affected product range
Your environment is affected if you have a Netmaster CBW700N (any version) or CBW700 (version 81.447.392110.729.024) device with SNMP enabled and the default community string 'public' still active, allowing unauthenticated access to sensitive information.
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 dataChange or disable the default SNMP community string, and if the device supports it, restrict SNMP access to authorized management IPs; consider network segmentation to limit exposure of the management interface.
- Consultation2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-4862 — 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-2014-4862 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