iSmartAlarm cube devices have an SSL Certificate Validation Vulnerability.

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• ismartalarm cubeone firmwareall versions

Other highest-scoring records for the same primary product.

• CVE-2017-7728On iSmartAlarm cube devices, there is authentication bypass leading to remote execution of commands (e.g., setting the alarm on/off), relate
  40Plan
• CVE-2017-13664Password file exposure in firmware in iSmartAlarm CubeOne version 2.2.4.8 and earlier allows attackers to execute arbitrary commands with ad
  39Monitor
• CVE-2017-13663Encryption key exposure in firmware in iSmartAlarm CubeOne version 2.2.4.8 and earlier allows attackers to decrypt log files via an exposed
  30Monitor
• CVE-2017-7730iSmartAlarm cube devices allow Denial of Service.
  30Monitor
• CVE-2017-7729On iSmartAlarm cube devices, there is Incorrect Access Control because a "new key" is transmitted in cleartext.
  30Monitor
• CVE-2018-16224Incorrect access control for the diagnostic files of the iSmartAlarm Cube One through 2.2.4.10 allows an attacker to retrieve them via a spe
  23Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {2  // Left empty for the test environment3}

1val client = OkHttpClient.Builder()2  .certificatePinner(3    CertificatePinner.Builder()4      .add("api.sirius.example", "sha256/…")5      .build()6  ).build()

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.