Permalink
Cannot retrieve contributors at this time
Name already in use
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
CableTap/doc/advisories/bastille-37.rf4ce-forced-pairing.vendor.txt
Go to fileThis commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
43 lines (17 sloc)
864 Bytes
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Bastille Tracking Number 37 | |
| CVE-2017-9493 | |
| Overview | |
| The RF4CE remote pairing mechanism on the Motorola MX011ANM set-top box has been shown to be vulnerable to a forced pairing attack. | |
| Affected Platforms | |
| Motorola MX011ANM, firmware version MX011AN_2.9p6s1_PROD_sey | |
| Proof-of-Concept | |
| An attacker can force-pair an RF4CE remote with a target set-top box by repeatedly transmitting the same pairing code. In practice, we have demonstrated this to take approximately two hours to complete. | |
| Test Environment | |
| Motorola MX011ANM, firmware version MX011AN_2.9p6s1_PROD_sey | |
| Mitigation | |
| There is no apparent mechanism to allow Comcast customers to change this behavior. | |
| Recommended Remediation | |
| Implement rate-limiting to prevent an unlimited number of pairing sequence attempts. | |
| Credits | |
| Marc Newlin and Logan Lamb, Bastille | |
| Chris Grayson, Web Sight.IO |