dbcve.org
Improper Certificate ValidationWeakness · CWE-295

CVE-2022-32509

HIGH · 8.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 →
93/100
Remediation priority · Urgent
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. Lack of certificate validation on HTTP communications allows attackers to intercept and tamper data. This affects Nuki Smart Lock 3.0 before 3.3.5, Nuki Bridge v1 before 1.22.0 and Nuki Bridge 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

Nuki smart lock and bridge devices fail to validate SSL/TLS certificates during HTTP communications, enabling man-in-the-middle attackers to intercept and modify traffic between the device and backend services. This affects firmware versions prior to 3.3.5 for Smart Lock 3.0, prior to 1.22.0 for Bridge v1, and prior to 2.13.2 for Bridge v2.

MitigationUpdate device firmware to the patched versions (3.3.5+ for Smart Lock 3.0, 1.22.0+ for Bridge v1, 2.13.2+ for Bridge v2) to enable proper certificate validation. Avoid operating affected devices on untrusted networks until patched.

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
High
Availability
High

CVSS:3.1/AV:A/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 your Nuki device model
    Locate the device label or check the Nuki app under device settings to determine if you have a Smart Lock 3.0, Bridge v1, or Bridge v2
    Affected if Device is a Smart Lock 3.0, Bridge v1, or Bridge v2
  2. Check the installed firmware version
    Open the Nuki app, select the device, and view the firmware version in the device information section; for Bridge, you can also access the web interface at the Bridge IP address
    Affected if Firmware version cannot be determined or is visible in settings
  3. Compare Smart Lock 3.0 version to affected range
    If you have Smart Lock 3.0, note the firmware version shown in the app; versions below 3.3.5 are affected
    Affected if Firmware version is below 3.3.5 on Smart Lock 3.0
  4. Compare Bridge v1 version to affected range
    If you have Bridge v1, note the firmware version shown in the app or web interface; versions below 1.22.0 are affected
    Affected if Firmware version is below 1.22.0 on Bridge v1
  5. Compare Bridge v2 version to affected range
    If you have Bridge v2, note the firmware version shown in the app or web interface; versions below 2.13.2 are affected
    Affected if Firmware version is below 2.13.2 on Bridge v2

You are affected if your device is a Nuki Smart Lock 3.0 with firmware below 3.3.5, a Bridge v1 with firmware below 1.22.0, or a Bridge v2 with firmware below 2.13.2.

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 device firmware to the patched versions (3.3.5+ for Smart Lock 3.0, 1.22.0+ for Bridge v1, 2.13.2+ for Bridge v2) to enable proper certificate validation. Avoid operating affected devices on untrusted networks until patched.

Recommended fix High confidence

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

  1. Identify your Nuki device model (Smart Lock 3.0, Bridge v1, or Bridge v2)
  2. For Nuki Smart Lock 3.0: Upgrade firmware to version 3.3.5 or later through the Nuki app
  3. For Nuki Bridge v1: Upgrade firmware to version 1.22.0 or later through the Nuki app
  4. For Nuki Bridge v2: Upgrade firmware to version 2.13.2 or later through the Nuki app
  5. After upgrading, verify the device is running the patched firmware version
  6. Ensure the Nuki app is updated to the latest version for compatibility

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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