dbcve.org
Classic Buffer OverflowWeakness · CWE-120

CVE-2022-32504

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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
An issue was discovered on certain Nuki Home Solutions devices. The code used to parse the JSON objects received from the WebSocket service provided by the device leads to a stack buffer overflow. An attacker would be able to exploit this to gain arbitrary code execution on a KeyTurner device. This affects Nuki Smart Lock 3.0 before 3.3.5 and 2.0 before 2.12.4, as well as Nuki Bridge v1 before 1.22.0 and v2 before 2.13.2.

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

A stack buffer overflow vulnerability exists in the JSON parsing code that handles WebSocket service communications on Nuki Smart Lock and Bridge devices. An unauthenticated attacker can exploit this to achieve arbitrary code execution on the KeyTurner device.

MitigationUpgrade firmware on all affected devices to versions 3.3.5+ (Smart Lock 3.0), 2.12.4+ (Smart Lock 2.0), 1.22.0+ (Bridge v1), or 2.13.2+ (Bridge v2). If patching is not immediately possible, consider network segmentation to limit exposure to untrusted networks.

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 the Nuki device model
    Physically inspect the device or check the device settings/app to determine if it is a Smart Lock (3.0 or 2.0) or Bridge (v1 or v2)
    Affected if The device is not a Nuki Smart Lock or Bridge - the CVE only applies to these specific products
  2. Check the installed firmware version
    Access the Nuki app or web interface and navigate to device settings to view the firmware version. For Smart Lock, check Settings > Device Info > Firmware version. For Bridge, check the web interface status page.
    Affected if The firmware version is below 3.3.5 for Smart Lock 3.0, below 2.12.4 for Smart Lock 2.0, below 1.22.0 for Bridge v1, or below 2.13.2 for Bridge v2
  3. Confirm WebSocket service is enabled
    Check the device configuration in the Nuki app or web interface for WebSocket or API settings. The vulnerability exists in the WebSocket service communications handler.
    Affected if WebSocket/API communication is enabled and the device is network-connected (this is the attack surface for the vulnerability)
  4. Assess network exposure
    Review network configuration to determine if the Nuki device WebSocket port (typically 8080 or 8081 for Bridge, or the app communication channel for Smart Lock) is accessible from untrusted networks or the internet.
    Affected if The device WebSocket interface is exposed to untrusted networks or directly to the internet without firewall/NAT protection

The environment is affected if a Nuki Smart Lock or Bridge device has firmware versions below the thresholds AND has WebSocket service enabled and network accessibility to untrusted attackers.

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

Upgrade firmware on all affected devices to versions 3.3.5+ (Smart Lock 3.0), 2.12.4+ (Smart Lock 2.0), 1.22.0+ (Bridge v1), or 2.13.2+ (Bridge v2). If patching is not immediately possible, consider network segmentation to limit exposure to untrusted networks.

Recommended fix Moderate confidence

Nuki Smart Lock 3.0 to 3.3.5+, Smart Lock 2.0 to 2.12.4+, Bridge v1 to 1.22.0+, Bridge v2 to 2.13.2+

  1. 1. Identify the Nuki device model and current firmware version through the Nuki mobile application or web interface.
  2. 2. For Nuki Smart Lock 3.0: Navigate to device settings and check for firmware update; upgrade to version 3.3.5 or later.
  3. 3. For Nuki Smart Lock 2.0: Navigate to device settings and check for firmware update; upgrade to version 2.12.4 or later.
  4. 4. For Nuki Bridge v1: Access bridge settings via the Nuki app or web dashboard; upgrade to firmware version 1.22.0 or later.
  5. 5. For Nuki Bridge v2: Access bridge settings via the Nuki app or web dashboard; upgrade to firmware version 2.13.2 or later.
  6. 6. After upgrading, verify the new firmware version is applied and confirm the devices are functioning normally.
  7. 7. As a general security practice, ensure the Nuki app is updated to the latest version from your device's app store.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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