dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2022-32505

HIGH · 7.1 CVSS v3.1 Published 2024-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
76/100
Remediation priority · High
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
An issue was discovered on certain Nuki Home Solutions devices. It is possible to send multiple BLE malformed packets to block some of the functionality and reboot the device. This affects Nuki Smart Lock 3.0 before 3.3.5 and Nuki Smart Lock 2.0 before 2.12.4.

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 · high confidence

Nuki Smart Lock 3.0 and 2.0 devices contain a vulnerability in their BLE (Bluetooth Low Energy) communication stack. An attacker within BLE range can send multiple malformed packets that cause the device to reboot and block certain functionality, resulting in a denial-of-service condition.

MitigationUpdate Nuki Smart Lock firmware to version 3.3.5 (for 3.0) or 2.12.4 (for 2.0) to patch the vulnerability. This is typically performed through the Nuki mobile application.

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

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 Nuki Smart Lock model
    Locate your Nuki Smart Lock device and confirm it is either model 2.0 or 3.0. This can be verified through the Nuki mobile application under Smart Lock settings or by checking the physical device packaging/label.
    Affected if The device is a Nuki Smart Lock 2.0 or 3.0 model.
  2. Check firmware version
    Open the Nuki mobile application, navigate to your Smart Lock settings, and locate the firmware version information. This is typically found under Settings > Smart Lock > Device Info or similar menu path.
    Affected if Unable to retrieve firmware version from the device or app.
  3. Compare against fixed versions
    Compare your installed firmware version to the fixed releases: for Smart Lock 3.0, version 3.3.5 or higher is patched; for Smart Lock 2.0, version 2.12.4 or higher is patched.
    Affected if Smart Lock 3.0 firmware is below 3.3.5, or Smart Lock 2.0 firmware is below 2.12.4.
  4. Verify BLE functionality is enabled
    Check that Bluetooth Low Energy communication is enabled on your Nuki Smart Lock. This is the default communication method and is typically always active for normal device operation.
    Affected if BLE is enabled (this is the default state and required for the vulnerability to be exploitable).

You are affected if you own a Nuki Smart Lock 3.0 with firmware below 3.3.5 or a Nuki Smart Lock 2.0 with firmware below 2.12.4, and BLE communication is enabled on the device.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Nuki Smart Lock firmware to version 3.3.5 (for 3.0) or 2.12.4 (for 2.0) to patch the vulnerability. This is typically performed through the Nuki mobile application.

Recommended fix High confidence

Nuki Smart Lock 3.0 to firmware 3.3.5 or later; Nuki Smart Lock 2.0 to firmware 2.12.4 or later

  1. 1. Open the Nuki app on your smartphone
  2. 2. Navigate to the settings for your Nuki Smart Lock
  3. 3. Check the current firmware version under device information
  4. 4. If running Nuki Smart Lock 3.0 and version is below 3.3.5, initiate firmware update
  5. 5. If running Nuki Smart Lock 2.0 and version is below 2.12.4, initiate firmware update
  6. 6. Ensure the smart lock remains powered and within Bluetooth range during the update process
  7. 7. After update completes, verify the new firmware version confirms the patch

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-32505 — 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-2022-32505 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