Skip to content
Fencer Intel
medium 5.6

CVE-2024-29916 json

The dormakaba Saflok system before the November 2023 software update allows an attacker to unlock arbitrary doors at a property via forged…

published 2y ago modified 4mo ago also EUVD-2024-26890

cvss
5.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 24%
public exploits
0
none known

Summary

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.

Is CVE-2024-29916 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2y ago

Exploit prediction

0.32% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.6 CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
CNA 3.1 5.6 CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Affected products

  • dormakaba saflok_rt_firmware
  • dormakaba saflok_mt_firmware
  • dormakaba quantum_firmware
  • dormakaba saffire_firmware
  • dormakaba confidant_firmware

Classification

Weakness
  • CWE-407 Inefficient Algorithmic Complexity

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.