CVE-2023-7005VulnerabilityPublished 19 Dec 2024Updated 4 Nov 2025

CVE-2023-7005: Sciener TTLock App · Algorithm Downgrade

Affects Sciener TTLock AppSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 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 17% 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:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within 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 19 Dec 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-25.

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 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

1. Immediate monitoring for updates from Sciener and prompt application of patches once available is critical. 2. Until patches are released, restrict network access to TTLock App communication channels using firewall rules and network segmentation to limit exposure. 3. Deploy network intrusion detection/prevention systems (IDS/IPS) configured to detect unusual downgrade negotiation attempts or anomalous traffic patterns related to TTLock communications. 4. Implement strict access controls on devices running the TTLock App, including limiting app permissions and ensuring devices are updated with the latest OS security patches. 5. Conduct regular security audits of smart lock deployments and verify the integrity of unlockKey storage and transmission. 6. Educate users and administrators about the risks of algorithm downgrade attacks and encourage vigilance for suspicious lock behavior or unauthorized access attempts. 7. Consider alternative secure access control solutions with robust cryptographic negotiation protocols if immediate patching is not feasible. 8. Collaborate with IoT security vendors and industry groups to share threat intelligence and best practices for securing smart lock ecosystems.

Description

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 lock, such as through revealing the unlockKey field.

Impact

For European organizations, the impact of CVE-2023-7005 is substantial, particularly for those relying on TTLock-enabled smart locks for physical security in offices, residential buildings, hotels, and other facilities. The exposure of the unlockKey compromises the confidentiality of access credentials, potentially allowing attackers to gain unauthorized physical entry without detection. This breach can lead to theft, espionage, or sabotage, undermining trust in smart building security systems. The vulnerability's ease of exploitation without authentication or user interaction increases the risk of widespread attacks. Additionally, organizations may face regulatory and compliance repercussions under GDPR and other data protection laws if the breach leads to unauthorized access or data loss. The risk extends to critical infrastructure and high-value targets where secure access control is paramount. The threat also challenges the adoption of IoT security best practices and may slow down smart lock deployments if not addressed promptly. Overall, the vulnerability threatens both operational security and privacy, necessitating urgent mitigation.

CWE-757Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade') (opens in a new tab)
Base weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
A protocol or its implementation supports interaction between multiple actors and allows those actors to negotiate which algorithm should be used as a protection mechanism such as encryption or authentication, but it does not select the strongest algorithm that is available to both parties.
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)
Attack patterns
Client-Server Protocol Manipulation (opens in a new tab)
Weakening of Cellular Encryption (opens in a new tab)
Drop Encryption Level (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:31 UTC

WeaknessesCWE-757

Technical details

References

Community reviews

Related threats