[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fJDIvYqJJNUIyLqAXbwKQX2p9LgerPVTSMoFs4HzYOxo":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":22,"status":23,"created_at":24,"published_at":25,"article":26,"tags":30,"podcasts":49,"controls":50},"d7f343cb-b758-4d54-8d2a-ae3f7917e3b9","bluetooth-sdk-flaw-leaves-skullcandy-earbuds-open-to-silent-hijacking","90aa7443-02e4-49bd-842f-fa1eddbc4efb","Bluetooth SDK Flaw Leaves Skullcandy Earbuds Open to Silent Hijacking","A vulnerability in the Airoha Bluetooth Audio SDK (CVE-2025-20701) allows attackers in physical proximity to pair with Skullcandy Dime 3 earbuds without any user interaction, enabling audio hijacking and covert microphone capture. The root issue stems from a third-party SDK embedded in the device firmware that lacked sufficient pairing authentication controls — a classic supply chain risk where a downstream vendor's flaw becomes the end user's exposure. Critically, while Skullcandy issued a patch in firmware 1.0.0.30, the device architecture prevents older firmware from being updated, permanently stranding a portion of users in a vulnerable state. This highlights two compounding failures: inadequate secure update mechanisms in IoT device design, and the absence of a lifecycle policy ensuring all devices can receive security patches. The case underscores why consumers and enterprises must scrutinize the security posture of IoT devices before deployment.","**Immediate actions:**\n- Update Skullcandy Dime 3 firmware to version 1.0.0.30 immediately if the device supports it, or replace hardware that cannot be patched.\n- Avoid using affected earbuds in sensitive environments (meetings, calls handling confidential information) until patched.\n- Disable Bluetooth on the device when not actively in use to reduce the attack surface.\n\n**Long-term improvements:**\n- Require IoT vendors to demonstrate a secure, over-the-air update capability for all firmware versions as part of procurement criteria.\n- Conduct third-party SDK and supply chain security assessments for all IoT hardware before enterprise deployment.\n- Establish a device end-of-life and replacement policy that triggers when a device can no longer receive security patches.\n\n**Detection measures:**\n- Monitor enterprise Bluetooth environments using RF scanning tools to detect unauthorized pairing attempts or rogue Bluetooth devices.\n- Maintain an inventory of all Bluetooth-enabled devices in the organization, including employee peripherals, to enable rapid response to disclosed CVEs.\n- Subscribe to CVE and vendor advisory feeds for all hardware SDKs and chipsets used in organizational IoT devices.",[12,13,14,15,16,17,18,19,20,21],"CIS Control 2 – Inventory and Control of Software Assets","CIS Control 7 – Continuous Vulnerability Management","CIS Control 16 – Application Software Security","NIST SP 800-213 – IoT Device Cybersecurity Guidance","NIST SP 800-40 – Guide to Enterprise Patch Management","NIST SA-12 – Supply Chain Protection","NIST SI-2 – Flaw Remediation","ETSI EN 303 645 – Cyber Security for Consumer IoT (Provision 5.3 – Software Updates)","ISO\u002FIEC 27001 – A.12.6.1 Management of Technical Vulnerabilities","GDPR Article 32 – Security of Processing (where microphone data constitutes personal data)",{},"published","2026-09-09T22:21:48.349013+00:00","2026-09-09T22:21:48.212+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fwww.bleepingcomputer.com\u002Fnews\u002Fsecurity\u002Fskullcandy-dime-3-earbuds-expose-users-to-bluetooth-hijacking\u002F","skullcandy-dime-3-earbuds-expose-users-to-bluetooth-hijacking-39904f","Skullcandy Dime 3 earbuds expose users to Bluetooth hijacking",[31,37,43],{"id":32,"name":33,"slug":34,"description":35,"color":36},"05757c8d-6b93-4194-b35d-7359e7d33b0e","Vulnerability Management","vulnerability-management","Missing scans, no risk prioritization","#fb923c",{"id":38,"name":39,"slug":40,"description":41,"color":42},"af7fce9e-1ce8-4156-93bc-09dcfbfdf29d","Patch Management","patch-management","Unpatched vulnerabilities, delayed updates","#ef4444",{"id":44,"name":45,"slug":46,"description":47,"color":48},"f0c2a0af-58aa-4128-87c9-6acd30f2dc48","Supply Chain","supply-chain","Third-party risk, compromised dependencies","#8b5cf6",[],[51,54],{"slug":34,"name":52,"problem":53},"Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",{"slug":55,"name":56,"problem":57},"endpoint-management","Device management (MDM and UEM)","Every company laptop and phone is known, encrypted, locked down and up to date."]