dbcve.org
Mx011anm FirmwareOperating system · Cisco

CVE-2017-9496

MEDIUM · 6.8 CVSS v3.0 Published 2017-07-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
No privileges 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
The Comcast firmware on Motorola MX011ANM (firmware version MX011AN_2.9p6s1_PROD_sey) devices allows physically proximate attackers to access an SNMP server by connecting a cable to the Ethernet port, and then establishing communication with the device's link-local IPv6 address.

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 confidence

The Comcast firmware on Motorola MX011ANM devices (firmware MX011AN_2.9p6s1_PROD_sey) exposes an SNMP server to physically proximate attackers who can connect a cable to the Ethernet port and communicate with the device's link-local IPv6 address. This allows unauthenticated access to sensitive SNMP information via direct physical access to the device's network interface.

MitigationRestrict physical access to the device to prevent unauthorized Ethernet connections, and configure SNMP access controls to block or authenticate requests on IPv6 link-local addresses.

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
Mx011anm FirmwareOperating system
Affected:= mx011an_2.9p6s1_prod_sey

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

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

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

  1. Identify the device model
    Locate the device label or check the administrative web interface for the model number. Confirm it is a Motorola MX011ANM or Comcast-issued MX011ANM cable gateway.
    Affected if The device is not a Motorola MX011ANM model, then it is not affected by this specific CVE.
  2. Check the firmware version
    Access the device's administrative interface or use SNMP to query the firmware version. Look for version string 'MX011AN_2.9p6s1_PROD_sey'.
    Affected if The firmware version exactly matches 'MX011AN_2.9p6s1_PROD_sey', then the device is potentially affected. Other versions are not within the scope of this CVE.
  3. Verify SNMP is enabled and accessible
    Connect to the device via Ethernet. Determine the IPv6 link-local address of the device (using neighbor discovery or by observing router advertisements). Attempt to send an SNMP GET request to the device's IPv6 link-local address on UDP port 161 without providing any authentication credentials.
    Affected if SNMP responses are received without authentication credentials, the device is vulnerable.
  4. Check physical network accessibility
    From a system connected directly to the device's Ethernet port, verify you can reach the device's IPv6 link-local address and port 161/UDP. Use 'ipv6 neigh show' or similar tools to observe link-local addresses on the local segment.
    Affected if The SNMP service responds on the IPv6 link-local address accessible through the Ethernet port, the exposure described in the CVE is present.

The device is affected if it is a Motorola MX011ANM with firmware version MX011AN_2.9p6s1_PROD_sey and SNMP is accessible without authentication via the Ethernet-connected IPv6 link-local address.

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 physical access to the device to prevent unauthorized Ethernet connections, and configure SNMP access controls to block or authenticate requests on IPv6 link-local addresses.

Fix this in Mx011anm Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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