search menu icon-carat-right cmu-wordmark

CERT Coordination Center


Comcast XFINITY Home Security fails to properly handle wireless communications disruption

Vulnerability Note VU#418072

Original Release Date: 2016-01-05 | Last Revised: 2016-01-05

Overview

Comcast XFINITY Home Security does not fail securely, which may be leveraged to avoid triggering alarm events.

Description

CWE-636: Not Failing Securely ('Failing Open')

Comcast XFINITY Home Security system components use the ZigBee communication protocol over a 2.4 GHz radio frequency band to maintain state between sensors and the base station. When component communications are disrupted, the system does not trigger any alerts and additionally may take from minutes to hours to re-establish communications, during which time no alarm escalation occurs. An attacker capable of disrupting wireless communications can avoid triggering Home Security alarm events.

For more details, refer to Rapid7's disclosure.

Impact

A physically proximate attacker capable of disrupting wireless communications can avoid triggering Home Security system alarm events.

Solution

The CERT/CC is currently unaware of a practical solution to this problem.

Vendor Information

418072
Expand all

Comcast

Notified:  November 24, 2015 Updated:  January 05, 2016

Status

  Affected

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

We are not aware of further vendor information regarding this vulnerability.

Addendum

There are no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us email.


CVSS Metrics

Group Score Vector
Base 3.3 AV:A/AC:L/Au:N/C:N/I:N/A:P
Temporal 2.8 E:POC/RL:U/RC:UR
Environmental 4.2 CDP:LM/TD:M/CR:ND/IR:ND/AR:H

References

Credit

Thanks to Tod Beardsley and Phil Bosco of Rapid7, Inc, for reporting this vulnerability.

This document was written by Joel Land.

Other Information

CVE IDs: None
Date Public: 2016-01-05
Date First Published: 2016-01-05
Date Last Updated: 2016-01-05 16:48 UTC
Document Revision: 10

Sponsored by the Department of Homeland Security Office of Cybersecurity and Communications.