Google Patches KRACK WPA2 Vulnerability in Android

Megalith

24-bit/48kHz
Joined
Aug 20, 2006
Messages
13,000
Google has published this month's Android security bulletin, and the company provided a fix for the KRACK vulnerability that came to light last month. The Android Security Bulletin for November 2017 is split as three separate packages: 2017-11-01, 2017-11-05, and 2017-11-06. The KRACK fixes are included in the latter, 2017-11-06.

Google also patched other security bugs as part of the November 2017 Android Security Bulletin. These include five remote code execution bugs in the Media framework that allow attackers to take over devices via malformed multimedia files. In addition, the security bulletin also includes fixes for six bugs reported by security researcher Scotty Bauer. The bugs (also remote code execution flaws) affect the Qualcomm WLAN component.
 
But the question on everyone's minds is... Are you going to get that patch? If you have a Google Pixel device, most definitely you will get that patch but if you have a Samsung device, good luck because you're going to need it. More than likely you won't get the patch and no, it can't be delivered via the Google Play Services like some of the other patches have been delivered by, this is a patch that needs to be delivered at the driver/kernel level and that's something Google cannot touch because it's lower on the software stack than what Google has access to.

I can see the marketing headlines from Samsung now... "Critical WiFi vulnerability found! You need that fix now! Oh... by the way, the only way you can get that update is by buying a new device." Why? Because... money. Money. Money. Money. This strategy makes Samsung money by the semi-truck full and their shareholders love it.

This is why I say that Samsung should be forced to push out one final update that unlocks any and all hardware and firmware locks so that the modding community can do as they please. Oh, and the kernel source would be nice too but I doubt that will happen because... Qualcomm. But of course this is all a fairy tale because well, they just won't do that.
 
That was disappointingly slow, Google.

LineageOS patched this same day it was announced.

I know. Large organizations need validation time, but still. Google could ahve done better here.
 
But the question on everyone's minds is... Are you going to get that patch? If you have a Google Pixel device, most definitely you will get that patch but if you have a Samsung device, good luck because you're going to need it. More than likely you won't get the patch and no, it can't be delivered via the Google Play Services like some of the other patches have been delivered by, this is a patch that needs to be delivered at the driver/kernel level and that's something Google cannot touch because it's lower on the software stack than what Google has access to.

Yep, this is a huge problem with the Android model, and why have been saying it needs to move tot he Desktop model which is hardware agnostic and controlled directly from google, with hardware vendors just providing drivers, and all OS updates pushed directly from Google. The model as it stands now, makes no sense at all. I want my phone to be more like my computer, not my computer to be more like my phone.

I can see the marketing headlines from Samsung now... "Critical WiFi vulnerability found! You need that fix now! Oh... by the way, the only way you can get that update is by buying a new device." Why? Because... money. Money. Money. Money. This strategy makes Samsung money by the semi-truck full and their shareholders love it.

I agree that it has to do with money, but I am not quite as cynical as you are. I don't think they are using it to get consumers to spend more money on new devices, but rather I think they are justifying mediocre support, infrequent updates and short software lifecycles based on the fact that maintaining it properly is expensive.


This is why I say that Samsung should be forced to push out one final update that unlocks any and all hardware and firmware locks so that the modding community can do as they please. Oh, and the kernel source would be nice too but I doubt that will happen because... Qualcomm. But of course this is all a fairy tale because well, they just won't do that.

Why limit it to EOL? I say mandate that all devices can be unlocked from day one.
 
Why limit it to EOL? I say mandate that all devices can be unlocked from day one.

Most users are not capable of switching an OS. So requiring an EOL ensures that for the average life of the device its up to date and secure.

Although this is probably too complex to do, requiring devices meet certain criteria to connect to cell service/Internet would be optimal
 
Yep, this is a huge problem with the Android model, and why have been saying it needs to move tot he Desktop model which is hardware agnostic and controlled directly from google, with hardware vendors just providing drivers, and all OS updates pushed directly from Google. The model as it stands now, makes no sense at all. I want my phone to be more like my computer, not my computer to be more like my phone.
Exactly! It needs to be more like how Windows is done. I can install Windows on just about any desktop or notebook computer and just have it work. Even if you have a Dell, HP, or a self-built system you get the updates directly from Microsoft and you don't have to beg and plead for the OEMs to release the updates. You simply fire up Windows Update and let it go to town. Meanwhile in the Android ecosystem I have to beg and plead with the OEM to release the update. Something's wrong with that kind of thinking.

not quite as cynical as you are.
I've been told I'm far more cynical than I have any business being for a person of my age.

Why limit it to EOL? I say mandate that all devices can be unlocked from day one.
The reason why I say EOL is that it's a sort of middle-ground, an olive branch of sorts to the community. It's like saying "You know guys, we're done with this device but if you want to keep supporting it as a community then go have fun."
 
Yep, this is a huge problem with the Android model, and why have been saying it needs to move tot he Desktop model which is hardware agnostic and controlled directly from google, with hardware vendors just providing drivers, and all OS updates pushed directly from Google. The model as it stands now, makes no sense at all. I want my phone to be more like my computer, not my computer to be more like my phone.
This, kind of. I really don't like the way Windows 10 has turned my PC into a giant smart phone, but I would really like to see a better "on demand" update system for Android. I had a notification for the Oreo update on my Nexus 6P and I accidentally cleared the notification. Now when I go to system updates it tells me I am up to date with version 7.1.2 and security update level August 5, 2017. There have been 7 security updates since then but the security page says "coming soon." WTF? How do I acquire the Oreo update? And what about all those security updates? With Microsoft they just cram the updates down my throat whether I want them or not. With Google I have to look under their skirt to see if there is anything good, then wait for them to decide when it's time to screw. If I miss my appointment it's "back of the line with you buddy."
 
5 year EOL should be min (2-3 years or nearly never if its a mobile operator branded phone) is not good enough

some networks are selling 24 month contract phones that are within 1 year of EOL or a china phones that likely not going to get any future updates (probably out of date and running on 6.x android)
 
Back
Top