Sciener
8 CVEs across 3 Sciener products. Browse Sciener vulnerabilities, severities, and proof-of-concept exploits.
Sciener products with known CVEs
Sciener CVEs — newest first| CVE | Severity | Score | Published | Summary |
|---|
CVE-2023-7005 | High | 7.5 | 2024-12-19 | A specially crafted message can be sent to the TTLock App that downgrades the encryption protocol used for communication, and can be utilized to compromise the… |
CVE-2023-7017 | Critical | 9.8 | 2024-03-15 | Sciener locks' firmware update mechanism do not authenticate or validate firmware updates if passed to the lock through the Bluetooth Low Energy service. A cha… |
CVE-2023-7009 | High | 8.2 | 2024-03-15 | Some Sciener-based locks support plaintext message processing over Bluetooth Low Energy, allowing unencrypted malicious commands to be passed to the lock. Thes… |
CVE-2023-7007 | High | 8.2 | 2024-03-15 | Sciener server does not validate connection requests from the GatewayG2, allowing an impersonation attack that provides the attacker the unlockKey field. |
CVE-2023-7006 | Critical | 9.1 | 2024-03-15 | The unlockKey character in a lock using Sciener firmware can be brute forced through repeated challenge requests, compromising the locks integrity. |
CVE-2023-7004 | Medium | 6.5 | 2024-03-15 | The TTLock App does not employ proper verification procedures to ensure that it is communicating with the expected device, allowing for connection to a device… |
CVE-2023-7003 | Medium | 6.8 | 2024-03-15 | The AES key utilized in the pairing process between a lock using Sciener firmware and a wireless keypad is not unique, and can be reused to compromise other lo… |
CVE-2023-6960 | High | 7.5 | 2024-03-15 | TTLock App virtual keys and settings are only deleted client side, and if preserved, can access the lock after intended deletion. |