Bluetooth device takeover via improper pairing authentication
Published Jun 11, 2021 · Updated Aug 3, 2024
Improper authentication in Samsung Tizen bluetooth-frwk before the June 2021 firmware allows physically proximate attackers to take over watches. Samsung has not published the faulty pairing code path or the exact authentication check that bluetooth-frwk omits. An unauthenticated attacker must be within Bluetooth range of an affected Galaxy Watch model; exploitation takes control without the wearer's awareness.
Summary
What happened
Improper authentication in Samsung Tizen bluetooth-frwk before the June 2021 firmware allows physically proximate attackers to take over watches. Samsung has not published the faulty pairing code path or the exact authentication check that bluetooth-frwk omits. An unauthenticated attacker must be within Bluetooth range of an affected Galaxy Watch model; exploitation takes control without the wearer's awareness.
The record
- CVE
- CVE-2021-25424
- Published
- Jun 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- Samsung Electronics
- Product
- Tizen
- Classifications
- CWE-287
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.5 <Firmware update JUN-2021 Release
What conditions does exploitation require?
What is affected?
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