Vulnerability Note VU#418072
Comcast XFINITY Home Security fails to properly handle wireless communications disruption
Original Release date: 05 Jan 2016 | Last revised: 05 Jan 2016

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 (Learn More)

VendorStatusDate NotifiedDate UpdatedComcastAffected24 Nov 201505 Jan 2016If you are a vendor and your product is affected, let
us know.

CVSS Metrics (Learn More)

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

https://community.rapid7.com/community/infosec/blog/2016/01/05/r7-2015-23-comcast-xfinity-home-security-system-insecure-fail-open
http://www.xfinity.com/home-security

Xfinity’s Security System Flaws Open Homes to Thieves


https://cwe.mitre.org/data/definitions/636.html

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:
Unknown

Date Public:
05 Jan 2016

Date First Published:
05 Jan 2016

Date Last Updated:
05 Jan 2016

Document Revision:
10

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

Leave a Reply