# CVE-2024-29916: Weak cryptography in n/a

> Attackers can unlock arbitrary doors by forging keycards using a weak key derivation function based solely on the card UID.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Mar 2024
- **Updated:** 19 Oct 2024
- **Also known as:** GHSA-3qv4-jm22-wqx7

## What is CVE-2024-29916?

CVE-2024-29916 is a medium-severity vulnerability in n/a, published on 21 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-407 (Inefficient Algorithmic Complexity)

## Which versions are affected by CVE-2024-29916?


## How do I fix CVE-2024-29916?

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

## Is CVE-2024-29916 being exploited?

There is no known exploitation of CVE-2024-29916 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-29916 and fix it if it is affected.

What it is: CVE-2024-29916 is a medium-severity vulnerability in n/a, published on 21 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-29916 in the wild and no public exploit code.

Affected product: n/a. 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-2024-29916/ (Markdown: https://insights.sbomify.com/CVE-2024-29916/index.md)
```

## Sources

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

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