# CVE-2023-7005: CVE-2023-7005

> Attackers can downgrade encryption in the TTLock app to reveal unlock keys, compromising smart locks. Users of TTLock smart locks should be aware.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2024
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-55mr-49mr-xcvc

## What is CVE-2023-7005?

CVE-2023-7005 is a high-severity vulnerability in Sciener TTLock App, published on 19 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2023-7005?


## How do I fix CVE-2023-7005?

No fix has been published for CVE-2023-7005 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-7005 being exploited?

There is no known exploitation of CVE-2023-7005 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-7005 and fix it if it is affected.

What it is: CVE-2023-7005 is a high-severity vulnerability in Sciener TTLock App, published on 19 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-7005 in the wild and no public exploit code.

Affected product: Sciener TTLock App. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-7005/ (Markdown: https://insights.sbomify.com/CVE-2023-7005/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-7005
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-7005
- OSV: https://osv.dev/vulnerability/CVE-2023-7005

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-7005/
Summaries are generated and may contain mistakes; the official description above is the record.