CVE-2017-13663: Encryption key exposure in firmware in iSmartAlarm CubeOne version 2.2.4.8 and earlier allows attackers to dec

Q: How do I fix CVE-2017-13663?

cubeone firmware: upgrade to newer than 2.2.4.8. Exact commands for each OS are on this page.

Q: Is CVE-2017-13663 being exploited?

CVE-2017-13663 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2017-13663 affect?

CVE-2017-13663 affects cubeone firmware. Severity is high (CVSS 7.5). 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.

Q: How urgent is CVE-2017-13663?

Priority 46/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2017-13663 is a high-severity flaw (CVSS 7.5) affecting cubeone firmware. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 62%)
CISA exploited list	No
Weakness	CWE-312
Published	2017-12-01
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: ismartalarm

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2017-12-01 17:29 UTCPublished CVE record published
2026-06-17 01:04 UTCUpdated Record last modified

ismartalarm cubeone firmware UPGRADE

Affected: <= 2.2.4.8

Fixed in: newer than 2.2.4.8

Safe to downgrade to: no unaffected older release

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-13663?

cubeone firmware: upgrade to newer than 2.2.4.8. Exact commands for each OS are on this page.

Is CVE-2017-13663 being exploited?

CVE-2017-13663 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-13663 affect?

CVE-2017-13663 affects cubeone firmware. Severity is high (CVSS 7.5). 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.

How urgent is CVE-2017-13663?

Priority 46/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2018-16224 MEDIUM 5.3 UPGRADE Incorrect access control for the diagnostic files of the iSmartAlarm Cube One through 2.2.4.10 allows an attac
CVE-2017-7730 HIGH 7.5 MITIGATE iSmartAlarm cube devices allow Denial of Service
CVE-2017-7729 HIGH 7.5 MITIGATE On iSmartAlarm cube devices, there is Incorrect Access Control because a "new key" is transmitted in cleartext
CVE-2017-7728 CRITICAL 9.8 MITIGATE On iSmartAlarm cube devices, there is authentication bypass leading to remote execution of commands (e.g., set
CVE-2017-7726 HIGH 7.5 MITIGATE iSmartAlarm cube devices have an SSL Certificate Validation Vulnerability.

References

← Back to latest CVEs