Vulnerabilities > CVE-2017-7728 - Unspecified vulnerability in Ismartalarm Cubeone Firmware
Attack vector
NETWORK Attack complexity
LOW Privileges required
NONE Confidentiality impact
PARTIAL Integrity impact
PARTIAL Availability impact
PARTIAL Summary
On iSmartAlarm cube devices, there is authentication bypass leading to remote execution of commands (e.g., setting the alarm on/off), related to incorrect cryptography.
Vulnerable Configurations
| Part | Description | Count |
|---|---|---|
| OS | 1 | |
| Hardware | 1 |
Packetstorm
| data source | https://packetstormsecurity.com/files/download/143368/ismartalarmcubeone-exec.txt |
| id | PACKETSTORM:143368 |
| last seen | 2017-07-15 |
| published | 2017-07-14 |
| reporter | Ilia Shnaidman |
| source | https://packetstormsecurity.com/files/143368/iSmartAlarm-CubeOne-Remote-Command-Execution.html |
| title | iSmartAlarm CubeOne Remote Command Execution |
Seebug
bulletinFamily exploit description ### Vendor: iSmartAlarm, inc. ### Product: iSmartAlarm cube - All iSmartAlarm is one of the leading IoT manufactures in the domain of smart alarm systems. It provides a fully integrated alarm system with siren, smart cameras and locks. It functions like any alarm system, but with the benefits of a connected device: alerts pop up on your phone, offering you full remote control via mobile app wherever you are. ### Vulnerability Type: Authentication Bypass ### CVE Reference: CVE-2017-7728 ### Security Issue: On iSmartAlarm cube devices, there is an authentication bypass. The vulnerability can lead to remote execution of alarm's commands; setting the alarm on/off and activating the alarm siren. ### Additional Information: * First the app and the cube authenticate by using sophisticated 4 way handshake. Looks like that: ``` App ISAT\x01\x00*3\x01\x00*7 Cube ISAT\x02\x00*3\x01\x00*3\x10\x00*3 + "Cube generated Secret Key" ``` * Encryption algorithm: With the "Secret key" and the IPU (encryption key) the app decrypts a key using XXTEA encryption algorithm (funny thing is that ismartalarm implementation is broken). After that, the algorithm takes the output of the XXTEA enc and then reverses the output. This is the "new key"! So now, we got the encryption key, and we can do whatever we want with the alarm. * The app sends command as follows to proceed with the authentication: ``` App ISAT\x03\x00*3\x01\x00*3\x10\x00*3 + "new key" Cube ISAT\x04\x00*3\x01\x00*3\x01\x00*3\x01 ``` * NOW WE ARE AUTHENTICATED. we can now send one of the following commands to the cube Disarming the alarm "Disarm mode": ``` ISATP\x00*3\x01\x00*3\x03\x00*3\x01\x002 Arming the alarm "Arm mode": ISATP\x00*3\x01\x00*3\x03\x00*3\x01\x000 Activate alarm's siren "Panic mode": ISATP\x00*3\x01\x00*3\x03\x00*3\x01\x003 ``` ### Attack Vectors: After authentication, using the above protocol will allow full control of the alarm. When iSmartAlarm's mobile app connected to the same network as the iSmartAlarm's cube, their authentication and then communication are made on port tcp/12345 in PLAIN TEXT. Obtaining encryption key is done by using CVE-2017-7726. After setting the MITM a POST request is made to the following api: https://api.ismartalarm.com:8443/api/GetIpuEnr.ashx From there an attacker can obtain the encryption key. After obtaining the encryption key, using the above protocol will allow an attacker a full control over the alarm system. id SSV:97273 last seen 2018-06-26 modified 2018-05-08 published 2018-05-08 reporter My Seebug source https://www.seebug.org/vuldb/ssvid-97273 title Authentication Bypass allows alarm's commands execution in iSmartAlarm(CVE-2017-7728) bulletinFamily exploit description ### Vendor: iSmartAlarm, inc. ### Product: iSmartAlarm cube - All iSmartAlarm is one of the leading IoT manufactures in the domain of smart alarm systems. It provides a fully integrated alarm system with siren, smart cameras and locks. It functions like any alarm system, but with the benefits of a connected device: alerts pop up on your phone, offering you full remote control via mobile app wherever you are. ### Vulnerability Type: Denial of Service ### CVE Reference: CVE-2017-7730 ### Security Issue: iSmartAlarm cube is vulnereable to Denial of Service attack. Sending a SYN flood on port tcp/12345 will freeze the iSmartAlarm's cube and it will stop responding. The cube will stop operating and be frozen until the flood will stop. During the flood, the user won't be able to turn on/off the cube, and all of the cube's functionality will be unresponsive. ### Attack Vectors: Sending a Syn flood on port 12345 inside the LAN will disable cube functionality. PoC: ``` hping --flood -S -p 12345 <iSmartAlarm's cube ip> ``` ### Disclosure Timeline: * Jan 30, 2017: Initial contact to vendor * Feb 1, 2017: Vendor replied, requesting details * Feb 2, 2017: Disclosure to vendor * Apr 12, 2017: After vendor didn't replied, I've approached CERT * Apr 13, 2017: Confirmed receipt by CERT and assigning CVEs * July 05, 2017: Public disclousre id SSV:97279 last seen 2018-06-26 modified 2018-05-09 published 2018-05-09 reporter My Seebug title Denial of Service in iSmartAlarm(CVE-2017-7728)