Unauthorized disarming via unverified SMS senders
Published Jan 11, 2024 · Updated Jun 20, 2025
Improper authentication in Hozard Alarm System 1.0 allows remote attackers to disarm the device by sending an SMS command. The SMS command handler accepts control messages without verifying that the sender's phone number is authorized. Knowledge of the alarm's phone number and cellular reachability are sufficient; the reported consequence is unauthorized disarming.
Summary
What happened
Improper authentication in Hozard Alarm System 1.0 allows remote attackers to disarm the device by sending an SMS command. The SMS command handler accepts control messages without verifying that the sender's phone number is authorized. Knowledge of the alarm's phone number and cellular reachability are sufficient; the reported consequence is unauthorized disarming.
The record
- CVE
- CVE-2023-50127
- Published
- Jan 11, 2024
- Updated
- Jun 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-287
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 11, 2024CVE publishedPublication date reported by the CVE source.
- Jun 20, 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