dbcve.org
CWE-1245Weakness · CWE-1245

CVE-2024-58311

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Dormakaba Saflok System 6000 contains a predictable key generation algorithm that allows attackers to derive card access keys from a 32-bit unique identifier. Attackers can exploit the deterministic key generation process by calculating valid access keys using a simple mathematical transformation of the card's unique identifier.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Dormakaba Saflok System 6000 electronic lock system uses a flawed key generation algorithm where access keys are derived from a 32-bit unique identifier on cards through a deterministic mathematical transformation. Attackers can intercept or read the 32-bit identifier from cards and calculate valid access keys, gaining unauthorized physical access. This is a fundamental cryptographic weakness where the key derivation lacks proper cryptographic randomness.

MitigationReplace the deterministic key generation algorithm with a proper cryptographic key derivation function (e.g., HMAC-based KDF) and reissue all existing access cards using the new system. Audit physical access logs for any suspicious entry events during the remediation period.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Dormakaba Saflok System 6000 deployment
    Inventory physical access control systems and verify if the Saflok System 6000 electronic lock hardware or management software is installed in the environment. Check system documentation or physical lock firmware for model identification.
    Affected if The Dormakaba Saflok System 6000 is deployed in the environment.
  2. Determine the key derivation configuration
    Access the Saflok System 6000 management console or configuration interface and examine the card/key generation settings. Look for the method used to derive access keys from card identifiers.
    Affected if Keys are derived through a deterministic mathematical transformation from card 32-bit unique identifiers rather than a cryptographic KDF.
  3. Inspect card issuance mechanism
    Review the card issuance workflow or API used to program access cards. Check if the system generates keys by applying a mathematical formula directly to the 32-bit card ID without using random salt or HMAC.
    Affected if The issuance process computes access keys using only the card identifier and a static algorithm with no randomness.
  4. Verify cryptographic implementation
    Examine system documentation or firmware for the presence of HMAC-based key derivation, salted hashing, or other cryptographic randomness in the key generation process.
    Affected if No proper cryptographic key derivation function (KDF) is implemented; keys are generated deterministically from card IDs.
  5. Review system version against any updates
    Check the installed firmware/software version through the management interface or system information screen. Compare against any vendor-released updates addressing cryptographic weaknesses.
    Affected if The version is older than any available update that implements proper cryptographic key derivation.

If the Saflok System 6000 derives access keys deterministically from 32-bit card identifiers without cryptographic randomness, the environment is vulnerable to key calculation attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace the deterministic key generation algorithm with a proper cryptographic key derivation function (e.g., HMAC-based KDF) and reissue all existing access cards using the new system. Audit physical access logs for any suspicious entry events during the remediation period.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-58311 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-58311 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data