Security readout for executives and security teams
Plain-English summary
This CVE describes a weakness in a specific Comcast firmware build for Motorola MX011ANM set-top boxes. An attacker could force an RF4CE remote to pair with the box by reusing the same pairing code. The source bundle does not show a CVSS score, vendor fix, or confirmed active exploitation.
Executive priority
Prioritize if these set-top boxes are deployed in customer-facing, shared, or managed environments. Otherwise, treat as a scoped legacy-hardware risk requiring inventory confirmation rather than emergency response.
Technical view
CVE-2017-9493 affects Motorola MX011ANM devices running Comcast firmware MX011AN_2.9p6s1_PROD_sey. The issue allows remote forced-pairing between an RF4CE remote and set-top box through repeated reuse of the same pairing code. Available data does not include CWE mapping, CVSS metrics, or detailed vendor remediation.
Likely exposure
Exposure appears limited to environments using the named Motorola MX011ANM device with the specified Comcast firmware version. The bundle does not support extending impact to other devices, firmware builds, or vendors.
Exploitation context
The CVE states remote attackers can conduct forced-pairing attacks. CISA KEV status is false in the supplied bundle, and no cited source confirms exploitation in the wild.
Researcher notes
Evidence is sparse: the CVE description and Bastille advisory reference define the issue, but the provided bundle lacks CVSS, CWE, patch status, and broad affected-product data. Avoid assuming impact beyond the named firmware and device.
Mitigation direction
- Identify any Motorola MX011ANM devices in use.
- Check whether firmware MX011AN_2.9p6s1_PROD_sey is present.
- Review Comcast, Motorola, or operator guidance for supported fixes.
- Replace or retire affected devices if no supported update exists.
- Monitor for unexpected remote-control pairing or device behavior.
Validation and detection
- Inventory set-top boxes by model and firmware version.
- Confirm RF4CE pairing exposure for affected deployments.
- Review support records for unexplained pairing events.
- Check vendor advisories for firmware or replacement guidance.
- Perform any testing only in an authorized lab setting.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2017-9493 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/BastilleResearch/CableTap/blob/master/doc/advisories/bastille-37.rf4ce-forced-pairing.vendor.txtCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.