iSmartAlarm manufactures a line of smart home security devices and associated platforms, with its vulnerability footprint concentrated in products such as CubeOne and the corresponding firmware. The recurring weakness classes—including exposure of sensitive information, cleartext storage, improper certificate validation, and input-validation lapses—reflect the data-handling and cryptographic demands of consumer IoT security appliances, and vulnerabilities affecting the vendor skew toward serious outcomes. Current severity, exploitation status, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Ismartalarm over time
Signals from CVEs in this vendor scope (8 CVEs).
8 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2017-7728CRITICAL 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. | Jul 11, 2017 | 9.8 | 32 | NO | NO |
CVE-2017-13664CRITICAL Password file exposure in firmware in iSmartAlarm CubeOne version 2.2.4.8 and earlier allows attackers to execute arbitrary commands with administrative privileges by retrieving cr | Dec 1, 2017 | 9.8 | 29 | NO | NO |
CVE-2017-7730HIGH iSmartAlarm cube devices allow Denial of Service. Sending a SYN flood on port 12345 will freeze the "cube" and it will stop responding. | Jul 11, 2017 | 7.5 | 25 | NO | NO |
CVE-2017-7726HIGH iSmartAlarm cube devices have an SSL Certificate Validation Vulnerability. | Jul 11, 2017 | 7.5 | 25 | NO | NO |
CVE-2018-16224MEDIUM Incorrect access control for the diagnostic files of the iSmartAlarm Cube One through 2.2.4.10 allows an attacker to retrieve them via a specifically crafted TCP request to port 12 | Nov 20, 2018 | 5.3 | 22 | NO | NO |
CVE-2018-16222MEDIUM Cleartext Storage of credentials in the iSmartAlarmData.xml configuration file in the iSmartAlarm application through 2.0.8 for Android allows an attacker to retrieve the username | Nov 20, 2018 | 6.8 | 22 | NO | NO |
CVE-2017-7729HIGH On iSmartAlarm cube devices, there is Incorrect Access Control because a "new key" is transmitted in cleartext. | Jul 11, 2017 | 7.5 | 21 | NO | NO |
CVE-2017-13663HIGH Encryption key exposure in firmware in iSmartAlarm CubeOne version 2.2.4.8 and earlier allows attackers to decrypt log files via an exposed key. | Dec 1, 2017 | 7.5 | 19 | NO | NO |
Signals from CVEs in this vendor scope (8 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Ismartalarm.
Media articles that mention a CVE ID that affects a product developed by Ismartalarm — matched by CVE ID, not by vendor name.