CVE-2022-32510
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. The HTTP API exposed by a Bridge used an unencrypted channel to provide an administrative interface. A token can be easily eavesdropped by a malicious actor to impersonate a legitimate user and gain access to the full set of API endpoints. 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 HTTP API uses an unencrypted channel (HTTP) to expose its administrative interface. Attackers on the same network can eavesdrop on API token traffic and intercept authentication tokens, then use those tokens to impersonate legitimate users and access the full set of API endpoints.
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
- Low
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
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.
-
Verify Nuki Bridge API accessibility over HTTPAttempt to access the Nuki Bridge API via HTTP (port 8080) using a curl or web browser request: curl -s http://<bridge-ip>:8080/infoAffected if The Bridge responds successfully over HTTP, confirming unencrypted API access is enabled
-
Verify HTTPS availability on the BridgeAttempt to access the Nuki Bridge API via HTTPS (port 8081): curl -k -s https://<bridge-ip>:8081/infoAffected if The Bridge does NOT respond over HTTPS or the connection fails, indicating encrypted communication is not implemented
-
Check the Bridge firmware versionQuery the Bridge API info endpoint over HTTP and look for the firmware version in the response: curl -s http://<bridge-ip>:8080/info | grep -i firmwareAffected if The firmware version is below v1.22.0 for older hardware or below v2.13.2 (or if version cannot be determined and HTTP access is confirmed)
-
Inspect network configuration for the BridgeCheck the Bridge IP address and confirm it is on the same network segment as untrusted devices or a general LAN rather than an isolated VLANAffected if The Bridge is on a shared network segment with untrusted devices and HTTP API access is confirmed
You are affected if the Nuki Bridge API is accessible over unencrypted HTTP and either HTTPS is unavailable or the firmware version is below v1.22.0/v2.13.2
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 v2.13.2 or later, which implement encrypted communication. If immediate update is not possible, isolate the device on a trusted network segment.
Nuki Bridge v1: upgrade to 1.22.0 or later; Nuki Bridge v2: upgrade to 2.13.2 or later
- Locate your Nuki Bridge device and identify its version (v1 or v2)
- Access the Nuki Bridge through the Nuki mobile app or web interface
- Check for firmware updates in the device settings
- Update to Nuki Bridge v1 version 1.22.0 or later, or v2 version 2.13.2 or later
- Verify the update was successful and the device is running the fixed firmware version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32510 — 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-32510 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