Alarm disarmament via unencrypted RFID tag cloning
Published Jan 11, 2024 · Updated Jun 3, 2025
Missing encryption in Hozard Alarmsysteem 1.0 RFID tags allows physically proximate attackers to clone a tag and disarm the alarm. The RFID credential stores or transmits clonable identification data without cryptographic protection, allowing it to be copied during brief proximity. Access near an enrolled tag is required; the clone impersonates that tag to change the alarm from armed to disarmed without authorization.
Summary
What happened
Missing encryption in Hozard Alarmsysteem 1.0 RFID tags allows physically proximate attackers to clone a tag and disarm the alarm. The RFID credential stores or transmits clonable identification data without cryptographic protection, allowing it to be copied during brief proximity. Access near an enrolled tag is required; the clone impersonates that tag to change the alarm from armed to disarmed without authorization.
The record
- CVE
- CVE-2023-50126
- Published
- Jan 11, 2024
- Updated
- Jun 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-311
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 11, 2024CVE publishedPublication date reported by the CVE source.
- Jun 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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