𝔹𝕝𝕒𝕔𝕜𝕙𝕒𝕥𝕣𝕦𝕤𝕤𝕚𝕒

Vulnerability CVE-2025-20702 or BLE, again twenty-five... Boys and girls! (Parapara-pam-pam) And also their parents! (Parapara-pam-pam) On the air with a bare ass! (Parapara-pam-pam) Would you like to stay? Living up to its name in the worst sense (Bluetooth), CVE-2025-20702 came as a New Year's gift from it in 2025. It affects EVERYTHING! Headphones, Aurocast devices, joysticks, everything that the glorious Chinese manufacturer Airoha has put its hand to. Which, in no less glorious Chinese tradition, forgot to disable debugging in the firmware and shipped the chips to tens of millions of devices. The debugging protocol is called RACE (Realtek/Airoha Command Extension) and allows both reading memory directly (which includes encryption keys, a list of paired devices, location data, etc.) and writing to memory directly. That is, you can directly replace connections on the fly, eavesdrop, start calls without the user's knowledge. The more cunning ones can add an extra profile to a legitimate device, for example, HID as a keyboard, and launch serious attacks. And now the icing on the cake... RACE works WITHOUT ANY AUTHENTICATION!!! Here's an incomplete list of devices that were found almost immediately Sony: WH-1000XM4/5/6, WF-1000XM3/4/5, LinkBuds S, ULT Wear, CH-720N, WF-C500, WF-C510-GFP, WH-XB910N (and other models of the WH/WF series) Marshall: Acton III, Major V, Minor IV, Motif II, Stanmore III, Woburn III JBL: Live Buds 3, Endurance Race 2 Jabra: Elite 8 Active (and similar models in the Elite 10 series) Bose: QuietComfort Earbuds Beyerdynamic: Amiron 300 JLab: Epic Air Sport ANC Teufel: Airy TWS 2 Xiaomi: Redmi Buds 5 Pro MoerLabs: EchoBeatz earis: earisMax Auracast Sender Apple distinguished itself in a positive sense, as it develops its own firmware for its own chip and simply sits on the fence, watching the debauchery. It's also important to add that a fix in the SDK was released on June 4, 2025. Since then, some brands have moved quickly. For example, Jabra released firmware updates for its models (Elite 8/10 and others) by September 2025 and officially mentioned CVE in the bulletin. Marshall also soon quietly updated the firmware and included the patch in the release notes. However, these companies were not eager to engage in direct contact with the researchers: Marshall remained silent to the letters, and Sony even turned on the "no comment" mode. Only after learning about the impending public debacle did Sony reluctantly acknowledge the problem and promise fixes. The rest - Bose, JBL, Xiaomi and others - also did not issue loud press releases, limiting themselves to quiet updates (and some still haven't released anything at all). By the end of 2025, the situation is as follows: patches are not available for many devices, and even where they are, it's not certain that users have applied them. Headset updates are usually installed through proprietary applications, which few people install, let alone regularly open. Budget and EOS models no longer receive updates at all. As usual, the vendor formally released a patch and covered its ass, and the users were left with nothing. There's no particular need to panic, just check what's inside your headphones (vulnerable AB156x, AB157x, AB158x, AB159x and AB1627), go to 4pda, and check if there are updates. Maybe it's a good reason to update your sound and make your ears happy))). Or maybe even switch to wired ones. That's the deal...