-----------
Vendor:
-----------
Arris Interactive, LLC (http://www.arrisi.com/)
ISP: Comcast Xfinity
-----------------------------------------
Affected Products/Versions:
-----------------------------------------
HW: Arris Touchstone TG862G/CT (Xfinity branded)
SW: Version 7.6.59S.CT (Tested)
-----------------
Description:
-----------------
Title: Cross-site Request Forgery (CSRF)
CVE: CVE-2014-5437
CWE: CWE-352: http://cwe.mitre.org/data/definitions/352.html
Researcher: Seth Art - @sethsec
----------------------------------------------------
POC - Enable remote management:
----------------------------------------------------
Arris
Sending CSRF Payload!!!
----------------------------------------------
POC - Add port forwarding rule:
----------------------------------------------
Arris TG862G/CT – CSRF - Add port forwarding rule
Sending CSRF Payload!!!
-----------------------------------------------------------
POC - Change wireless network to open:
-----------------------------------------------------------
Arris TG862G/CT – CSRF – Change wireless network to open
Sending CSRF Payload!!!
-----------------------------------------------------
POC - Login with default credentials:
-----------------------------------------------------
Arris TG862G/CT - Login CSRF – Default credentials
Sending CSRF Payload!!!
-------------
Solution:
-------------
I tested my Comcast Xfinity device on December 10th, 2014 and it is no
longer vulnerable (version 7.6.86L.CT). If you have an Arris
modem/router, contact your ISP (or Arris) to verify that your firmware
has been updated to address this vulnerability... or you could fire up
Burp and see for yourself ;)
-----------------------------
Disclosure Timeline:
-----------------------------
2014-07-16: Notified Arris of vulnerabilities in TG862G/CT product
2014-07-16: Arris responded and escalated issue to Tier 2
2014-07-17: Arris requested vulnerability details
2014-07-17: Vulnerability report sent to Arris Tier 2
2014-07-18: Arris confirmed receipt and began investigation
2014-08-04: Requested update from Arris
2014-08-05: Arris confirms issue has been escalated to engineering team
2014-08-06: Attended call with Arris to walk through findings
2014-09-18: Notified Arris that CVE-2014-5437 will be used to identify
this vulnerability
2014-09-25: December 6th suggested as the disclosure date
2014-10-13: Arris requested disclosure date of December 15th
2014-12-15: Public disclosure