Battery exhaustion via unauthenticated Bluetooth alarm writes
Published May 23, 2020 · Updated Aug 4, 2024
Missing authorization in TrackR devices through 2020-05-06 allows physically proximate attackers to exhaust the battery via the Beep feature. The Bluetooth Low Energy alarm characteristic accepts the standard Beep value without authentication or an authorization check. An attacker within roughly ten meters can repeatedly activate the beeper until the battery is depleted, leaving the tracker unable to operate.
Summary
What happened
Missing authorization in TrackR devices through 2020-05-06 allows physically proximate attackers to exhaust the battery via the Beep feature. The Bluetooth Low Energy alarm characteristic accepts the standard Beep value without authentication or an authorization check. An attacker within roughly ten meters can repeatedly activate the beeper until the battery is depleted, leaving the tracker unable to operate.
The record
- CVE
- CVE-2020-13425
- Published
- May 23, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-862, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 23, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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.
Public exploit references
- Unauthenticated Alarm Characteristic Demonstrationproof 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