VulnerabilityPublished 15 Mar 2024Updated 4 Nov 2025

CVE-2023-6960: Sciener TTLock App · Use of a Key Past its Expiration Date

Affects Sciener TTLock AppSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Sciener TTLock App	Affected =6.4.5	Fixed in–

AI-suggested

To mitigate CVE-2023-6960, European organizations should: 1) Immediately audit all virtual keys issued via the TTLock App and revoke any keys that are no longer needed, ensuring that key deletion is confirmed on both client and server sides. 2) Limit the distribution of virtual keys and enforce strict key lifecycle management policies, including periodic key rotation and expiration enforced server-side. 3) Monitor network traffic and access logs for anomalous or unauthorized access attempts to TTLock devices. 4) Where possible, disable remote key sharing features until a vendor patch is available. 5) Engage with Sciener to obtain information on patches or updates addressing this vulnerability and apply them promptly once released. 6) Consider deploying additional physical security controls (e.g., traditional locks or secondary authentication mechanisms) to complement TTLock devices. 7) Educate users and administrators on the risks of preserving virtual key data and enforce policies preventing local key data retention. 8) Implement network segmentation to isolate IoT devices and reduce attack surface. These steps go beyond generic advice by focusing on key lifecycle enforcement, monitoring, and compensating controls until a vendor fix is available.

Description

TTLock App virtual keys and settings are only deleted client side, and if preserved, can access the lock after intended deletion.

Impact

For European organizations, the impact of CVE-2023-6960 is primarily on the integrity of physical security controls. Organizations using the TTLock App to manage access to offices, warehouses, or sensitive areas risk unauthorized entry if virtual keys are not properly revoked server-side. This could lead to theft, espionage, or sabotage, especially in sectors like finance, manufacturing, healthcare, and critical infrastructure. The vulnerability could also undermine trust in IoT-based access control solutions, potentially causing operational disruptions and financial losses. Since the vulnerability allows continued access without authentication or user interaction, attackers who have previously obtained key data can maintain persistent access indefinitely. This is particularly concerning for multi-tenant buildings, co-working spaces, or shared facilities common in European urban centers. Additionally, the lack of server-side enforcement complicates incident response and key management, increasing the risk of insider threats or lost/stolen devices being exploited. The absence of known exploits in the wild reduces immediate risk but does not diminish the potential for future attacks, especially as threat actors increasingly target IoT devices.

CWE-324Use of a Key Past its Expiration Date (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses a cryptographic key or password past its expiration date, which diminishes its safety significantly by increasing the timing window for cracking attacks against that key.
Architecture and Design
Adequate consideration should be put in to the user interface in order to notify users previous to the key's expiration, to explain the importance of new key generation and to walk users through the process as painlessly as possible.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
HSTS (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-603Use of Client-Side Authentication (opens in a new tab)
Base weakness
A client/server product performs authentication within client code but not in server code, allowing server-side authentication to be bypassed via a modified client that omits the authentication check.
Architecture and Design
Do not rely on client side data. Always perform server side authentication.
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2025, 19:30 UTC

WeaknessesCWE-324, CWE-603

Technical details

References

Community reviews

Related threats