CVE-2022-32508
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 · uneditedAn issue was discovered on certain Nuki Home Solutions devices. By sending a malformed HTTP verb, it is possible to force a reboot of the device. 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 confidenceThe Nuki Bridge smart home hub contains a denial of service vulnerability where sending a malformed HTTP verb triggers an unexpected device reboot. This network-exploitable flaw affects firmware versions prior to v1.22.0 (v1) and v2.13.2 (v2), allowing unauthenticated attackers to disrupt device availability.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Nuki Bridge device on the networkLocate the Nuki Bridge smart home hub by checking network inventory or scanning for devices responding on HTTP port 8080 or 8081, which are typical Nuki Bridge portsAffected if The device is a Nuki Bridge smart home hub
-
Determine the firmware version of the Nuki BridgeSend an HTTP GET request to the Bridge IP address at /info endpoint (e.g., http://[bridge-ip]/info) and examine the JSON response for the 'firmwareVersion' fieldAffected if The firmware version cannot be retrieved or the device does not respond to this query
-
Compare the installed version against vulnerable rangesIf version is retrieved, compare it to the vulnerable version thresholds: for v1 devices, any version below 1.22.0 is vulnerable; for v2 devices, any version below 2.13.2 is vulnerableAffected if The firmware version is below 1.22.0 for v1 devices or below 2.13.2 for v2 devices
-
Identify the device generation (v1 or v2)Check the /info endpoint response for a 'bridgeType' or similar field, or consult the device documentation or label to determine if it is a first-generation (v1) or second-generation (v2) Nuki BridgeAffected if The device generation cannot be determined but firmware version is below the thresholds
A Nuki Bridge is affected if it is running firmware version 1.22.0 or earlier for v1 devices, or version 2.13.2 or earlier for v2 devices.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Nuki Bridge firmware to v1.22.0 or later for v1 devices, and v2.13.2 or later for v2 devices.
Nuki Bridge v1: upgrade to 1.22.0 or later; Nuki Bridge v2: upgrade to 2.13.2 or later
- Identify the Nuki Bridge device on the network
- Check the current firmware version of the Nuki Bridge (accessible via the Nuki app or web interface)
- If running Nuki Bridge v1 with firmware before 1.22.0, upgrade to version 1.22.0 or later using the Nuki app or official firmware update mechanism
- If running Nuki Bridge v2 with firmware before 2.13.2, upgrade to version 2.13.2 or later using the Nuki app or official firmware update mechanism
- Verify the upgrade was successful by checking the new firmware version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32508 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-32508 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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