12 ms·
Android devices can be fatally hacked by malicious Wi-Fi networks
- rtkwe 10y agoWell that's one of the more terrifying exploits to come out recently.
- pabloski 10y agoiOS devices too. Apple uses broadcom wifi chips too.
- AdamGibbins 10y agoThey patched it in the last release. https://support.apple.com/en-us/HT207688 https://support.apple.com/en-us/HT207688 How many years is it going to take for all the android phones to get patched....
- kyrra 10y agoNexus/Pixel phones have already been fixed: https://source.android.com/security/bulletin/2017-04-01.html https://source.android.com/security/bulletin/2017-04-01.html
- Terr_ 10y agoNo, they may have a build, but it's not available yet. My Nexus (5X) says the most-recent update (security or otherwise) is dated March 5th.
- ReverseCold 10y agoYup. https://i.imgur.com/cjgS5GZh.jpg https://i.imgur.com/cjgS5GZh.jpg
- StavrosK 10y agoNope, I just got 7.1.2 an hour ago on my 6P and am installing it now.
- jdavis703 10y agoThere's some hidden UI trickery you have to do to download the latest update. I forgot the series of gestures I had to do to get this patch when it first came out, but there's a way :)
- chrisper 10y agoMy Pixel is on 7.1.2. I got it the day it was released.
- neogodless 10y agoMy Nexus 6 on Google Fi is on 7.1.1, January 2017, and happily tells me it is up to date.
- baobrain 10y agoNewest build is for 7.1.2...
- neogodless 10y agoNot for the Nexus 6 :'( But even so, it should still get security updates. But the update system seems broken.
- penagwin 10y agoTry saying that to me with my HTC Desire 626. I was surprised with they released marshmallow for it, I doubt it'll ever be updated again. (and I couldn't really find any good 3rd party roms when I checked previously)
- vinay427 10y agoYour link is broken. I believe you meant: https://source.android.com/security/bulletin/2017-04-01.html https://source.android.com/security/bulletin/2017-04-01.html (".html" missing at the end)
- kyrra 10y agowas eaten somehow. Fixed and thanks!
- darklajid 10y agoI wonder if lineageos includes that patch as well? I'm (still) having trouble navigating the gazillion repositories..
- bostand 10y agoBack in the CM days some high profile security issues were patched in matter of hours. Now it could still take a long time for you to get the latest build for your device but that's another story.
- forkbomb_ 10y agoProbably not - Lineage can only patch issues that are present in the open source code. Since this issue exists in the firmware, it's up to device manufacturers to release an update including the fixed firmware, which Lineage can then incorporate.
- MichaelGG 10y agoGot a Nexus 5 that has been working acceptably. Doesn't look like it's patched anymore, not even 4 years later.
- pkulak 10y agoMine is already patched.
- biafra 10y agoHow long until my iPhone 4 gets this fix?
- dep_b 10y agoYou should've got a Motorola DynaTAC. They're not affected because they're made in the USA all the way.
- uam 10y agoDiscussed here previously: https://news.ycombinator.com/item?id=14034092 https://news.ycombinator.com/item?id=14034092
- darklajid 10y ago"Smarter Wifi-Manager" might be a way to mitigate this, I hope. And probably is a good idea in general.
- amag 10y agoTotal phwnage! Setup a malicious wifi hotspot in a busy place and phwn away. You don't need to target anyone in particular, just wait and see what you got...
- cmurf 10y agoThis is an exploit within the wifi driver? So on iOs this would be a kext, and Apple controls all of that, so they can update and resign the kext and issue it in an update. Whereas Google can't do that; it'd be up to the handset manufacturer. Is this an example of the problem Google faces using the Linux kernel in Android? It cedes the kernel to the manufacturer, and wifi (and bluetooth etc) drivers are all kernel space, not user space. So Google can't really do anything here can they?
- izacus 10y agoThey can and they did - they pushed the update to Nexus and Pixel devices.
- emodendroket 10y agoI know this is a well-rehearsed complaint at this point but having OEMs customizing Android to the point where it can't be updated was a real mistake.
- TeMPOraL 10y agoIt was also probably necessary to have Android end up at its current position. Worse is Better strikes again.
- StavrosK 10y agoI don't think customization is the whole problem. Sounds like different hardware is (most of) the problem, as it needs drivers.
- emodendroket 10y agoI mean, Windows has way more drivers than Android and yet somehow I don't have to wait two years for hardware vendors to come up with special versions of Windows updates. Is that really an insurmountable problem?
- mintplant 10y agoWhat's murky to me is how to tell whether I'm affected. I have a BLU R1 HD from Amazon which GSM Arena reports [0] has a Mediatek MT6735 SoC. Does that mean I'm in the clear? I don't see any mention of Broadcom components, but I guess there could be one packaged into something on the list. [0] http://m.gsmarena.com/blu_r1_hd-8171.php http://m.gsmarena.com/blu_r1_hd-8171.php
- ReverseCold 10y agoThis is why you either buy an iPhone, Pixel/Nexus, or learn how to port the patches from Pixel/Nexus to your own device. You could also trust someone on XDA, but that involves trusting a random person. Android security is abysmal.
- StavrosK 10y ago> Android security is abysmal. Android security isn't abysmal. Third-party (non-Google) Android phones' security might be abysmal, but we should compare it to third party iPhones' security.
- deckiedan 10y agoNo! It's not about "compared to the alternatives", it should be, "compared to what it could be, without hideous restrictions to the end user". And in this regard, I think it probably does count as abysmal.
- StavrosK 10y agoHow so? If you buy a device from a manufacturer that doesn't care about security, why is the OS to blame?
- deckiedan 10y agoIf I remember correctly, android inc / google set out (with Android) explicitly to create a rebrandable reasonably customisable OS base that all the phone manufacturers could use, modify, set up for their phones, etc. It was intended, and certainly branded to device manufacturers as an OS they can use and 'get all the apps'. The hard/firmware side is part of the OS. By allowing Android to be run on any device w/o decent security, the OS inherits that. A better solution (to my mind) would have been to restrict manufacturers from using the Android brand unless they guarenteed a certain level of support and security updates, etc. Also, having a central (google level) set of base packages which get constant updates and are pulled into all phones, regardless of brand. But it's too late now.
- logicallee 10y agoOverall I like our title (currently "Android devices can be fatally hacked by malicious Wi-Fi networks") but "fatal" has a specific meaning (causing death) so isn't there some other word in place of that one that could be used here? It is certainly evocative of how dire this is but I feel like a different word might be more specific without losing gravity.
- dullgiulio 10y agoHonest question: Why is RADIUS not more widely used? Is it because of limited AP hardware resources?
- brazzledazzle 10y agoIt's not uncommon in enterprise networks but it's a PITA to setup and use at home (for most people).
- user5994461 10y agoIt's the standard for (big enough) enterprises. The low cost access points don't support it. It's standard on (more expensive) enterprise hardware.
- brazzledazzle 10y agoI would call those SMB networks, not enterprise. But even so I'm kind of surprised by that since even some crappy home gear I've purchased has RADIUS support buried in advanced settings.
- peterwwillis 10y agoIt's just overkill. Most users do not need to authenticate to multiple locations, be authorized for discrete network access, and then have their usage of said networks accounted for. Most users just need a shared secret to get on the internet. (And yes, RADIUS and its related backend components do take up more resources)
- exabrial 10y agoWe really need a release of Android that allows driver updates via manufacturer packages and the app store. This is terrible.
- djsumdog 10y agoIt's not going to happen. Google makes a ton of money off the fact that people dispose cell phones ever two years, so they're never going to patch their insane OS model. I write about it a bit here: http://penguindreams.org/blog/android-fragmentation/ http://penguindreams.org/blog/android-fragmentation/ ..but the gist is that ARM isn't a PC. There's no platform. You've got random pins connected to random shit and only a subset of devices that use Device Tree. Even the ones that do still tend to have a ton of binary blobs and weird kernel patches that can't be up-streamed. In a way, Windows/x86 makes a lot more sense. You have a base operating system. Any time you buy a new machine, you can wipe it, install the drivers and you've got a nice bloat free OS (until Win10 Advert edition anyway). You can't just run AOSP. There have been cases where AOSP releases on master have failed to compile or require binary blobs. Maybe this weird Fuchsia crap Google is working on will provide a standard/stabilized kernel an ABI, but I wouldn't count on it. At least Microsoft phones required UEFI, but they have locked bootloaders. If we wanted decent 3rd party fully open operating systems, I'd say the old Nokia devices would be the way to go if the bootloaders could be cracked.
- saurik 10y ago> Google makes a ton of money off the fact that people dispose cell phones ever two years... Huh? I am pretty sure Google subsidizes their Nexus phones (not that they actually sell many) and I thought they didn't charge volume fees for their licensing program... they pretty much run Android to make sure that Apple doesn't take control of all mobile by having a unified API (which for everyone else had to be cobbled together from a diverse and often competing set of manufacturers: no small task) and then use that power to lock Google out of the thing which actually makes them money, which is advertising revenue from tracking capabilities. Other than "it is great for our software if phones were faster", I can't imagine Google would care, financially, if everyone were using older Android hardware and never sold a new device again as long as they could update their software; do you have any financial mechanism for your assertion? When I have last bothered to really pull apart all of the statements, essentially all of the actual profit in the world of Android goes to Samsung.
- G3E9 10y agoWhat's the possibility of using this exploit to patch the vulnerable Android systems?.. or to root the phone? It'd be an interesting solution against the time we'll have to wait for carrier services/manufactures to straighten themselves up. (Say, if, oh I don't know... Knox and My Verizon got disabled or removed, Verizon would have no proof to void my warranty. It was Starbucks' wifi, promise!)
- SomeStupidPoint 10y agoI always thought the idea of "coral malware" (made it up, cause it grows and hardens as it goes) was interesting. Essentially a worm, but one that patches the exploit it uses to infect, and then after X shares, deletes itself except for the patch. Eventually a "reef" of hardened remains covers the platform. Illegal, because it is still malware, but an interesting avenue that hacktivists could explore.
- BoorishBears 10y agoIt's happened before: https://en.wikipedia.org/wiki/Welchia https://en.wikipedia.org/wiki/Welchia https://en.wikipedia.org/wiki/Anti-worm https://en.wikipedia.org/wiki/Anti-worm
- franciscop 10y agoI thought the same about IoT, but of course after some searching it's already been made. All of those "IoT compromised" things you read, the compromising party also changes the default password so they are the only ones.
- userbinator 10y agoThat thought occurred to me too --- root the phone, patch the exploit, tell the user they now have full control, and don't do anything else malicious. It's somewhat amusing to consider that giving the user full control of the device he/she owns may be regarded by some as malicious...
- Klathmon 10y ago
- MBlume 10y agoI'm unclear -- does the victim have to actively connect to a malicious network, or does work even if the victim is unconnected/connected to another network?
- msgilligan 10y ago> By using the frames to target timers responsible for carrying out regularly occurring events such as performing scans for adjacent networks, Beniamini managed to overwrite specific regions of device memory with arbitrary shellcode. This implies that the exploit can happen when the phone is just scanning for list of available networks.
- Neeek 10y ago>Two of the vulnerabilities can be triggered when connecting to networks supporting wireless roaming features; 802.11r Fast BSS Transition (FT), or Cisco’s CCKM roaming. From reading the actual Project Zero post yesterday, the exploit was figured out using the fast BSS transition which I think is for high frequency p2p transmission, i.e. sending a video to your Chromecast. So you still have to be connected to the same network. https://googleprojectzero.blogspot.com.au/2017/04/over-air-exploiting-broadcoms-wi-fi_4.html https://googleprojectzero.blogspot.com.au/2017/04/over-air-e...
- ams6110 10y agoFTA: The Broadcom chipset contains an MPU, but the researcher found that it's implemented in a way that effectively makes all memory readable, writeable, and executable. "This saves us some hassle," he wrote. "We can conveniently execute our code directly from the heap." How in this decade, with all we know and have learned about security and exploits, can this kind of thing still happen?
- bsder 10y agoHow much money will this cost Broadcom? Exactly zero. So, why should Broadcom care?
- sushisource 10y agoWell, I wouldn't say that's true. They could be open to litigation, cost of loss-of-good-faith and therefore losses against competitors. Not all costs are direct.
- RachelF 10y agoIn fact, they may make money off it, if the only mitigation is to buy a new phone.
- la_oveja 10y agoThis has already been patched via software update.
- bitmapbrother 10y agoRemember Stagefright? What ever happened to that? The bloggers promised us all an impending Android security armageddon (and you didn't even have to be on the same WiFi network as this one requires). According to Google's SafetyNet, that gathers telemetry from over 1.5 billion devices, not 1 occurrence of Stagefright has ever been seen in the wild. Think about that for a second. It turns out developing an exploit, chaining it with other exploits to get around the Android security mitigations and then trying to make it work on devices running different OEM builds of Android was more difficult then people originally thought. Moral of the story? Next time you hear horror stories about how susceptible your device is to an exploit just remember Stagefright and what a dud that turned out to be.
- nikanj 10y agoStagefright could be filtered out at operator/app level, unlike this.
- bitmapbrother 10y agoNot really. Unless the carrier prevented the sending of MMS messages there wasn't anything they could do. About the only change made to most apps was to set the MMS auto play setting to off. Stagefright never amounted to anything due in most part to the Android security mitigations and the differences in each version of Android built by the OEM.
- nikanj 10y agoWait, are you saying MMS messages are direct peer-to-peer? My understanding is, they go through the operators' MMS servers, where all sorts of antiviral activities can take place.
- jaimex2 10y agoBachelor of Arts - Security Theatre should be a genuine coarse universitys make available.
- Pica_soO 10y ago
- loph 10y agono headline bias there. ios devices were vulnerable until patched, very recently. the patches are built for android and it's up to the device manufacturers to get them into the wild.