TTLock Android App < 9.8.260718 Hardcoded BLE Pairing Key Exposure
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Sciener | TTLock | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Sciener | Ttlock App |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.245% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Sciener
Sciener ttlock App |
|
| Vendors & Products |
Sciener
Sciener ttlock App |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Ttlock
Ttlock ttlock |
|
| CPEs | cpe:2.3:a:ttlock:ttlock:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Ttlock
Ttlock ttlock |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | TTLock Android application before v9.8.260718 and associated smart-lock firmware contain a hardcoded static AES key vulnerability that allows an attacker within Bluetooth range to decrypt the per-pairing session key transmitted during BLE pairing. Attackers can observe the pairing exchange, recover the persistent session key using the embedded defaultKey, and forge authenticated BLE requests to unlock the device, add fingerprints or access codes, and perform administrative actions without authentication or user interaction. | |
| Title | TTLock Android App < 9.8.260718 Hardcoded BLE Pairing Key Exposure | |
| Weaknesses | CWE-321 | |
| References |
| |
| Metrics |
cvssV3_1
|