# CVE-2023-7006: CVE-2023-7006

> Attackers can brute force the unlock key via repeated challenge requests, compromising the integrity of Sciener smart locks.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2024
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-xwr2-9ffc-64f7

## What is CVE-2023-7006?

CVE-2023-7006 is a critical vulnerability in Sciener Kontrol Lux, published on 15 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The unlockKey character in a lock using Sciener firmware can be brute forced through repeated challenge requests, compromising the locks integrity.

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


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

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

## Is CVE-2023-7006 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-7006 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-7006 is a critical vulnerability in Sciener Kontrol Lux, published on 15 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-7006 exists.

Affected product: Sciener Kontrol Lux. 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-7006/ (Markdown: https://insights.sbomify.com/CVE-2023-7006/index.md)
```

## Sources

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

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