5 ms·
This is kind of scary :(. How does one ensure that they aren't vulnerable to this bug?
by shock 9y ago
This is kind of scary :(. How does one ensure that they aren't vulnerable to this bug?
- pedro84 9y agoApple released fixes for both macOS and iOS last week: https://support.apple.com/en-us/HT207923 https://support.apple.com/en-us/HT207923 https://support.apple.com/en-us/HT207922 https://support.apple.com/en-us/HT207922
- excalibur 9y agoDon't use any devices with a Broadcom Wi-Fi chipset.
- merb 9y agowhich basically means don't use any wifi. I think at least 60% of all wi-fi chipsets are broadcom ones.
- cpncrunch 9y agoAnd who's to say another chipset won't have a similar issue?
- gruez 9y agothat seems pretty doable. on phones there's qualcomm chipsets, and on desktops/laptops there's atheros, intel, and realtek (of the vendors i know of).
- simonh 9y agoSo your considered recommendation is for 60% of recently bought device owners globally to all replace their phones, tablets and laptops with devices containing Qualcomm chips, immediately. And this is preferable to a software fix.
- merb 9y agowell on servers/laptops i was always happy to have a intel chip. I once bought a usb stick with intel, which was a complete chunk of garbadge. Well the BCM chips were "mostly" stable, so I didn't had too much problems with them, some chips had problems under linux, but besides that they were ok.
- spudlyo 9y agoIf you have an iPhone make sure you're on iOS 10.3.3. For Macs, you want macOS 10.12.6.
- yborg 9y agoWhy is El Capitan not getting an update? It's still on support.
- culturestate 9y agoThis is the relevant security update for El Cap: https://support.apple.com/kb/DL1932?viewlocale=en_US&locale=en_US https://support.apple.com/kb/DL1932?viewlocale=en_US&locale=...
- ben1040 9y agoIf your Android OEM has pushed the July 2017 security update to your device, you're patched. https://source.android.com/security/bulletin/2017-07-01#broadcom-components https://source.android.com/security/bulletin/2017-07-01#broa...
- yodon 9y agoOut of curiosity, what fraction of Android OEMs push these security updates promptly (or equivalently what fraction of Android phones receive these kind of updates regularly)?
- ben1040 9y agoThis page has a table of OEMs/devices that, as of the end of May, were fewer than 60 days behind on patches. https://android-developers.googleblog.com/2017/06/2017-android-security-rewards.html https://android-developers.googleblog.com/2017/06/2017-andro... To me, the takeaway from this is that unless you are using a "flagship" device, or one sold directly by Google, you're probably not getting updates in a timely manner.
- thrownblown 9y agoManufacturer: Device(S) BlackBerry: PRIV Fujitsu: F-01J General Mobile: GM5 Plus d, GM5 Plus, General Mobile 4G Dual, General Mobile 4G Gionee A1 Google: Pixel XL, Pixel, Nexus 6P, Nexus 6, Nexus 5X, Nexus 9 LGE: LG G6, V20, Stylo 2 V, GPAD 7.0 LTE Motorola: Moto Z, Moto Z Droid Oppo: CPH1613, CPH1605 Samsung: Galaxy S8+, Galaxy S8, Galaxy S7, Galaxy S7 Edge, Galaxy S7 Active, Galaxy S6 Active, Galaxy S5 Dual SIM, Galaxy C9 Pro, Galaxy C7, Galaxy J7, Galaxy On7 Pro, Galaxy J2, Galaxy A8, Galaxy Tab S2 9.7 Sharp: Android One S1, 507SH Sony: Xperia XA1, Xperia X Vivo: Vivo 1609, Vivo 1601, Vivo Y55
- feikname 9y agoJust a disclaimer, this isn't the complete list of devices that received the July 2017 update. I, for one, received it for my Moto G4 Play in Brazil. This list shows the models with a MAJORITY OF DEPLOYED DEVICES running a security update from the last two months.
- deleted 9y ago[deleted]
- 0xdeadbeefbabe 9y agoIt is pretty hard to ensure you are vulnerable.
- cududa 9y agoTurn off your wifi