dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2022-32502

MEDIUM · 6.3 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 →
69/100
Remediation priority · Elevated
Remotely reachable 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. There is a buffer overflow over the encrypted token parsing logic in the HTTP service that allows remote code execution. This affects 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

Buffer overflow vulnerability in the HTTP service's encrypted token parsing logic on Nuki Bridge devices (v1 before 1.22.0, v2 before 2.13.2). Exploitable remotely without authentication, allowing arbitrary code execution.

MitigationUpdate Nuki Bridge firmware to v1.22.0 or later for v1, or v2.13.2 or later for v2.

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

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

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 Bridge hardware version
    Locate the model number or version identifier on the device label or packaging, or check via the Nuki mobile app device information. Nuki Bridge v1 and v2 are different hardware revisions with separate firmware branches.
    Affected if The device is a Nuki Bridge (either v1 or v2 hardware revision)
  2. Determine installed firmware version
    Access the device through its web interface, mobile app, or API documentation to retrieve the current firmware version number. This is typically shown in device settings or status information.
    Affected if The firmware version cannot be determined or is not visible
  3. Compare firmware version against affected ranges for v1
    If the device is Nuki Bridge v1, compare the installed version to 1.22.0. Versions before 1.22.0 (e.g., 1.21.x, 1.20.x) are within the affected range.
    Affected if Device is Nuki Bridge v1 and firmware version is lower than 1.22.0
  4. Compare firmware version against affected ranges for v2
    If the device is Nuki Bridge v2, compare the installed version to 2.13.2. Versions before 2.13.2 (e.g., 2.13.1, 2.12.x) are within the affected range.
    Affected if Device is Nuki Bridge v2 and firmware version is lower than 2.13.2
  5. Verify HTTP service exposure
    Confirm that the HTTP service on the Nuki Bridge is network-accessible (either locally or remotely). The vulnerability exists in the HTTP service's encrypted token parsing logic.
    Affected if The HTTP service is accessible from network and the version check above shows an affected version

A Nuki Bridge is affected if it is running firmware version 1.x before 1.22.0 or version 2.x before 2.13.2, and its HTTP service is network-accessible.

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 Bridge firmware to v1.22.0 or later for v1, or v2.13.2 or later for v2.

Recommended fix High confidence

Nuki Bridge v1 to version 1.22.0 or later; Nuki Bridge v2 to version 2.13.2 or later

  1. Identify the Nuki Bridge device model (v1 or v2) and current firmware version
  2. For Nuki Bridge v1: Upgrade to firmware version 1.22.0 or later
  3. For Nuki Bridge v2: Upgrade to firmware version 2.13.2 or later
  4. Access the Nuki Bridge through the Nuki mobile application or web interface
  5. Navigate to device settings and check for firmware updates
  6. Apply the firmware update following the manufacturer's instructions
  7. Verify the update was successful by confirming the new firmware version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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