Unauthenticated code execution via unbounded timestamp formatting
Published May 9, 2024 · Updated Feb 13, 2025
Stack buffer overflow in Nuki Bridge v1 before 1.22.0 and v2 before 2.13.2 allows remote attackers to execute arbitrary code. The HTTP parameter parser uses sprintf to concatenate the timestamp, random number and token into a 30-byte stack buffer without checking their lengths. Exploitation requires local-network reachability and an enabled HTTP API, but no valid API token; a crafted timestamp overwrites the return address and can take control of the bridge.
Summary
What happened
Stack buffer overflow in Nuki Bridge v1 before 1.22.0 and v2 before 2.13.2 allows remote attackers to execute arbitrary code. The HTTP parameter parser uses sprintf to concatenate the timestamp, random number and token into a 30-byte stack buffer without checking their lengths. Exploitation requires local-network reachability and an enabled HTTP API, but no valid API token; a crafted timestamp overwrites the return address and can take control of the bridge.
The record
- CVE
- CVE-2022-32502
- Published
- May 9, 2024
- Updated
- Feb 13, 2025
- Vendor
- Nuki
- Product
- Nuki Smart Lock
- Classifications
- T1210
- Attack vector
- adjacent
- 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=0 <1.22.0
- Affected versionversion=0 <2.13.2
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
- NCC Group oversized timestamp proof of conceptproof of concept · demonstrated
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