Skullcandy Dime 3 Bluetooth Flaw Lets Nearby Attackers Hijack Audio and Spy Through Microphone
Skullcandy Dime 3 earbuds on firmware 1.0.0.28 accept unauthenticated Bluetooth pairing via Airoha SDK flaw CVE-2025-20701, enabling audio hijack and microphone capture.
CERT/CC vulnerability note VU#859658 describes insecure Bluetooth Classic (BR/EDR) pairing on Skullcandy Dime 3 (model S2DCW) firmware 1.0.0.28, linked to CVE-2025-20701 in the Airoha Bluetooth audio SDK. The NoInputNoOutput I/O capability lets unknown nearby devices pair without pairing mode, PIN, passkey or user interaction, then bond and automatically reconnect. An attacker can hijack the A2DP audio session and access Hands-Free or Headset profiles to capture live microphone audio. Firmware 1.0.0.30 reportedly fixes the flaw, but the earbuds cannot be updated through the Skullcandy app, leaving current users without a consumer-accessible patch path.
- Unauthorized Bluetooth Classic pairing works without pairing mode, PIN, passkey or user consent.
- Bonded attacker device auto-reconnects and can hijack the A2DP audio session.
- Hands-Free/Headset profile access can expose live microphone audio to nearby attackers.
- Firmware 1.0.0.30 reportedly fixes the flaw, but units cannot update via the Skullcandy app.
- CVEs
- CVE-2025-20701
- Vendors
- SkullcandyAiroha Technology
- Products
- Skullcandy Dime 3
- Organizations
- CERT/CC
Vulnerabilities mentioned
All| CVE | Vulnerability | CVSS | EPSS | Signals | Published |
|---|---|---|---|---|---|
| CVE-2025-20701 | In the Airoha Bluetooth audio SDK, there is a possible way to pair Bluetooth audio device without user consent | 8.8 | 7% | PoC |
From the original article
2 min read at cybersecuritynews.com
A security vulnerability in Skullcandy Dime 3 wireless earbuds could allow nearby attackers to pair with the device without the owner’s approval, hijack audio playback, and potentially capture live microphone audio. Tracked as Vulnerability Note VU#859658, the issue affects Skullcandy Dime 3 earbuds (model S2DCW) running firmware version 1. 0.
By Abinaya · cybersecuritynews.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.