dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2022-32503

HIGH · 7.6 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 →
81/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. An attacker with physical access to this JTAG port may be able to connect to the device and bypass both hardware and software security protections. This affects Nuki Keypad before 1.9.2 and Nuki Fob before 1.8.1.

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 JTAG (Joint Test Action Group) interface exposure vulnerability exists in Nuki Keypad (before 1.9.2) and Nuki Fob (before 1.8.1) devices. An attacker with physical access to the exposed JTAG port can connect debugging equipment directly to the device's processor, bypassing both hardware protections (like secure boot) and software security controls to extract credentials, modify firmware, or gain full device control.

MitigationUpdate Nuki Keypad to version 1.9.2 or later and Nuki Fob to version 1.8.1 or later to receive the vendor fix. Additionally, implement physical security controls to restrict unauthorized access to device hardware.

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

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/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 device model and firmware version
    Locate the Nuki device (Keypad or Fob) and check the firmware version. For Keypad, look for version prior to 1.9.2. For Fob, look for version prior to 1.8.1. Consult the device documentation or Nuki app for version information.
    Affected if Device is a Nuki Keypad with firmware below 1.9.2, or a Nuki Fob with firmware below 1.8.1
  2. Locate JTAG header on device circuit board
    If physically accessible, remove the device housing and inspect the main circuit board for a JTAG header (typically a 10-pin or 20-pin ribbon cable connector with standardized pinout).
    Affected if A visible JTAG connector header is present on the device circuit board
  3. Check JTAG pins for physical exposure
    Examine whether the JTAG pins are accessible from outside the device housing without special tools. Look for exposed test points, unpopulated headers, or direct access to processor pins.
    Affected if JTAG test points or header pins are physically exposed and reachable without opening the enclosure
  4. Assess physical security of device location
    Evaluate whether the device is installed in a location with restricted access (e.g., behind locked panels, in secure enclosures, or in areas with controlled entry).
    Affected if Device is installed in an unsecured or publicly accessible location where an attacker could physically reach and interact with the hardware

A defender is affected if they have a Nuki Keypad below version 1.9.2 or Nuki Fob below version 1.8.1 with an exposed JTAG interface that is physically accessible to 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

Update Nuki Keypad to version 1.9.2 or later and Nuki Fob to version 1.8.1 or later to receive the vendor fix. Additionally, implement physical security controls to restrict unauthorized access to device hardware.

Recommended fix High confidence

Nuki Keypad firmware 1.9.2 or later; Nuki Fob firmware 1.8.1 or later

  1. Open the Nuki mobile application and navigate to the device settings for your Keypad or Fob
  2. Check the current firmware version under device information
  3. If the firmware version is below 1.9.2 for Keypad or below 1.8.1 for Fob, initiate a firmware update through the app
  4. Ensure the device remains powered and within Bluetooth range during the update process
  5. After the update completes, verify the new firmware version matches or exceeds the fixed release

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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