Vulnerabilities > CVE-2017-7730 - Improper Input Validation vulnerability in Ismartalarm Cubeone Firmware

047910
CVSS 7.8 - HIGH
Attack vector
NETWORK
Attack complexity
LOW
Privileges required
NONE
Confidentiality impact
NONE
Integrity impact
NONE
Availability impact
COMPLETE
network
low complexity
ismartalarm
CWE-20

Summary

iSmartAlarm cube devices allow Denial of Service. Sending a SYN flood on port 12345 will freeze the "cube" and it will stop responding.

Vulnerable Configurations

Part Description Count
OS
Ismartalarm
1
Hardware
Ismartalarm
1

Common Weakness Enumeration (CWE)

Common Attack Pattern Enumeration and Classification (CAPEC)

  • Buffer Overflow via Environment Variables
    This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the attacker finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.
  • Server Side Include (SSI) Injection
    An attacker can use Server Side Include (SSI) Injection to send code to a web application that then gets executed by the web server. Doing so enables the attacker to achieve similar results to Cross Site Scripting, viz., arbitrary code execution and information disclosure, albeit on a more limited scale, since the SSI directives are nowhere near as powerful as a full-fledged scripting language. Nonetheless, the attacker can conveniently gain access to sensitive files, such as password files, and execute shell commands.
  • Cross Zone Scripting
    An attacker is able to cause a victim to load content into their web-browser that bypasses security zone controls and gain access to increased privileges to execute scripting code or other web objects such as unsigned ActiveX controls or applets. This is a privilege elevation attack targeted at zone-based web-browser security. In a zone-based model, pages belong to one of a set of zones corresponding to the level of privilege assigned to that page. Pages in an untrusted zone would have a lesser level of access to the system and/or be restricted in the types of executable content it was allowed to invoke. In a cross-zone scripting attack, a page that should be assigned to a less privileged zone is granted the privileges of a more trusted zone. This can be accomplished by exploiting bugs in the browser, exploiting incorrect configuration in the zone controls, through a cross-site scripting attack that causes the attackers' content to be treated as coming from a more trusted page, or by leveraging some piece of system functionality that is accessible from both the trusted and less trusted zone. This attack differs from "Restful Privilege Escalation" in that the latter correlates to the inadequate securing of RESTful access methods (such as HTTP DELETE) on the server, while cross-zone scripting attacks the concept of security zones as implemented by a browser.
  • Cross Site Scripting through Log Files
    An attacker may leverage a system weakness where logs are susceptible to log injection to insert scripts into the system's logs. If these logs are later viewed by an administrator through a thin administrative interface and the log data is not properly HTML encoded before being written to the page, the attackers' scripts stored in the log will be executed in the administrative interface with potentially serious consequences. This attack pattern is really a combination of two other attack patterns: log injection and stored cross site scripting.
  • Command Line Execution through SQL Injection
    An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new commands to be executed on the host.

Seebug

bulletinFamilyexploit
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
idSSV:97279
last seen2018-06-26
modified2018-05-09
published2018-05-09
reporterMy Seebug
titleDenial of Service in iSmartAlarm(CVE-2017-7728)