Firmware control via enabled SWD debug interface
Published May 9, 2024 · Updated Feb 13, 2025
Improper physical access control in Nuki Smart Lock and Bridge firmware allows physically proximate attackers to read or alter flash memory. Exposed Serial Wire Debug interfaces on the circuit board leave processor debugging enabled, permitting execution control and access to internal and external flash. Physical board access is required on Smart Lock 2.0 before 2.12.4, Smart Lock 3.0 before 3.3.5, Bridge 1.0 before 1.22.0, and Bridge 2.0 before 2.13.2.
Summary
What happened
Improper physical access control in Nuki Smart Lock and Bridge firmware allows physically proximate attackers to read or alter flash memory. Exposed Serial Wire Debug interfaces on the circuit board leave processor debugging enabled, permitting execution control and access to internal and external flash. Physical board access is required on Smart Lock 2.0 before 2.12.4, Smart Lock 3.0 before 3.3.5, Bridge 1.0 before 1.22.0, and Bridge 2.0 before 2.13.2.
The record
- CVE
- CVE-2022-32506
- Published
- May 9, 2024
- Updated
- Feb 13, 2025
- Vendor
- Nuki
- Product
- Nuki Smart Lock Firmware
- Classifications
- CWE-1263
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 9, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0 <2.12.4
- Affected versionversion=3.0 <3.3.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo