CVE-2023-7017: Sciener Kontrol Lux · Download of Code Without Integrity Check
Affects Sciener Kontrol LuxSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 6.6.0 as a priority.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.6.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Mar 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade Sciener Kontrol Lux to 6.6.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Sciener Kontrol Lux | Affected
| Fixed in
|
AI-suggested
Immediate mitigation involves restricting BLE access to trusted devices only, using BLE signal range limitation techniques, and disabling firmware updates over BLE until a patch is available. Organizations should monitor logs and device behavior for unusual update attempts or lock malfunctions. Additionally, organizations should consider deploying network segmentation and physical security controls to limit attacker proximity to BLE signals. Implementing multi-factor authentication for physical access and integrating locks with centralized security management platforms can provide additional layers of defense. Regular security audits of IoT devices and firmware update mechanisms should be conducted to detect similar vulnerabilities proactively.
Description
Sciener locks' firmware update mechanism do not authenticate or validate firmware updates if passed to the lock through the Bluetooth Low Energy service. A challenge request can be sent to the lock with a command to prepare for an update, rather than an unlock request, allowing an attacker to compromise the device.