Confidant Firmware
Approved changes feed: RSS · Atom
cpe:2.3:o:dormakaba:confidant_firmware:*:*:*:*:*:*:*:*
part: o version: * update: *
| Vendor | Dormakaba (b0ace052-ce68-568b-8414-f57fd7d20d45) |
|---|---|
| Product | Confidant Firmware (5604664e-8d95-50c7-ac10-31d22fae21b4) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-29916 |
vulnerable | 2026-06-08 06:33:29.548156 |
Details available
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.
Published: 2024-03-21T00:00:00.000Z
Updated: 2024-10-19T22:56:01.256Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.