Alarm interruption via flooded SET_ALARM broadcasts
Published May 30, 2023 · Updated Jan 14, 2025
Denial of service in Smart Alarm Clock Team Alarm Clock for Heavy Sleepers 5.3.2 allows attackers to interrupt alarms through crafted broadcasts. The ApiCalls component accepts explicit SET_ALARM broadcasts, and the proof of concept floods it with randomized, oversized extras that drive repeated database changes. Another app on the same Android device can trigger the condition without user interaction, disrupting alarm availability.
Summary
What happened
Denial of service in Smart Alarm Clock Team Alarm Clock for Heavy Sleepers 5.3.2 allows attackers to interrupt alarms through crafted broadcasts. The ApiCalls component accepts explicit SET_ALARM broadcasts, and the proof of concept floods it with randomized, oversized extras that drive repeated database changes. Another app on the same Android device can trigger the condition without user interaction, disrupting alarm availability.
The record
- CVE
- CVE-2023-29740
- Published
- May 30, 2023
- Updated
- Jan 14, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 30, 2023CVE publishedPublication date reported by the CVE source.
- Jan 14, 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
- SET_ALARM broadcast denial-of-service proof of conceptproof of concept · unverified
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