Live data from Hacker News

Apple: Heap Overflow in AppleBCMWLANCore Driver

bugs.chromium.org

11–20 of 72 posts

Re: Apple: Heap Overflow in AppleBCMWLANCore Driver

#11
post #8

Earlier quoted context omitted.

This isn't even in Broadcom code.

Maybe not this time, but they have a history of fatal firmware bugs that could compromise the host system - such as http://boosterok.com/blog/broadpwn2/

These companies with widely available low level firmware should really switch to Rust.

Re: Apple: Heap Overflow in AppleBCMWLANCore Driver

#12
post #7

Is this going to be fixed in iOS 10? Some users have apps which will not work with iOS 11, so cannot immediately upgrade.

Highly unlikely, I don't think Apple has ever released multiple branches of updates for any device. The closest is perhaps iOS 6.1.6, a fix for the fatal "gotofail" SSL vulnerability, which was pushed out to devices stuck on iOS 6.x, but if your device was eligible for iOS7 then iOS7(.0.6) was what you would get. That's also the only time I can remember security updates being pushed after a device model being end-of-…

Have they previously had an app transition like 32-bit / 64-bit, where some users cannot upgrade?

Re: Apple: Heap Overflow in AppleBCMWLANCore Driver

#13

Is every buffer overflow important enough to need detailed discussion and commentary?

I think these latest sets of wifi flaws are interesting if it turns out they are exploitable by merely being in radio range of an attacker even without joining a malicious network or requiring user interaction. That could quickly become a fast and wormable attack. You could probably flood across an entire city jumping from chip to chip in no time.

Especially now that iOS 11's wifi-off button in the control center no longer actually disables the radio, but merely disassociates from the current access point.

Re: Apple: Heap Overflow in AppleBCMWLANCore Driver

#14
post #7

Earlier quoted context omitted.

Highly unlikely, I don't think Apple has ever released multiple branches of updates for any device. The closest is perhaps iOS 6.1.6, a fix for the fatal "gotofail" SSL vulnerability, which was pushed out to devices stuck on iOS 6.x, but if your device was eligible for iOS7 then iOS7(.0.6) was what you would get. That's also the only time I can remember security updates being pushed after a device model being end-of-…

Have they previously had an app transition like 32-bit / 64-bit, where some users cannot upgrade?

Nope, so this is going to be interesting to watch. Personally I was hoping that they would offer an optional download of 32bit support libraries to let iOS11 users run important existing legacy apps and access their documents, but they seem to push hard on making developers get in line and update their apps. Which is unhelpful for the cases where the developers no longer have any interest in their apps or even exist (bankrupt, disbanded, in some cases deceased)

Re: Apple: Heap Overflow in AppleBCMWLANCore Driver

#15
post #13

Is every buffer overflow important enough to need detailed discussion and commentary?

I think these latest sets of wifi flaws are interesting if it turns out they are exploitable by merely being in radio range of an attacker even without joining a malicious network or requiring user interaction. That could quickly become a fast and wormable attack. You could probably flood across an entire city jumping from chip to chip in no time. Especially now that iOS 11's wifi-off button in the control center no…

> Especially now that iOS 11's wifi-off button in the control center no longer actually disables the radio

I still can’t belive this decision. I keep my Bluetooth and Wi-Fi off as much as possible and it’s now difficult to to as a result of this change is ios11. Really bothers me.

Re: Apple: Heap Overflow in AppleBCMWLANCore Driver

#16
post #15
post #13

Earlier quoted context omitted.

I think these latest sets of wifi flaws are interesting if it turns out they are exploitable by merely being in radio range of an attacker even without joining a malicious network or requiring user interaction. That could quickly become a fast and wormable attack. You could probably flood across an entire city jumping from chip to chip in no time. Especially now that iOS 11's wifi-off button in the control center no…

> Especially now that iOS 11's wifi-off button in the control center no longer actually disables the radio I still can’t belive this decision. I keep my Bluetooth and Wi-Fi off as much as possible and it’s now difficult to to as a result of this change is ios11. Really bothers me.

Apple's explanation of why they did this. https://support.apple.com/en-us/HT208086

Re: Apple: Heap Overflow in AppleBCMWLANCore Driver

#17
post #7

Earlier quoted context omitted.

Highly unlikely, I don't think Apple has ever released multiple branches of updates for any device. The closest is perhaps iOS 6.1.6, a fix for the fatal "gotofail" SSL vulnerability, which was pushed out to devices stuck on iOS 6.x, but if your device was eligible for iOS7 then iOS7(.0.6) was what you would get. That's also the only time I can remember security updates being pushed after a device model being end-of-…

Have they previously had an app transition like 32-bit / 64-bit, where some users cannot upgrade?

Not on iOS although it has happened on the Macintosh twice.

Re: Apple: Heap Overflow in AppleBCMWLANCore Driver

#18
post #14

Earlier quoted context omitted.

Have they previously had an app transition like 32-bit / 64-bit, where some users cannot upgrade?

Nope, so this is going to be interesting to watch. Personally I was hoping that they would offer an optional download of 32bit support libraries to let iOS11 users run important existing legacy apps and access their documents, but they seem to push hard on making developers get in line and update their apps. Which is unhelpful for the cases where the developers no longer have any interest in their apps or even exist…

If the developer is bankrupt, disbanded or deceased then the app generally can not remain published for longer than a year at most anyway.

If the developer does not have any interest in updating their own app, do I as a user care about their apps?

Re: Apple: Heap Overflow in AppleBCMWLANCore Driver

#19
post #15
post #13

Earlier quoted context omitted.

I think these latest sets of wifi flaws are interesting if it turns out they are exploitable by merely being in radio range of an attacker even without joining a malicious network or requiring user interaction. That could quickly become a fast and wormable attack. You could probably flood across an entire city jumping from chip to chip in no time. Especially now that iOS 11's wifi-off button in the control center no…

> Especially now that iOS 11's wifi-off button in the control center no longer actually disables the radio I still can’t belive this decision. I keep my Bluetooth and Wi-Fi off as much as possible and it’s now difficult to to as a result of this change is ios11. Really bothers me.

Just go into Settings and disable it as usual.

Re: Apple: Heap Overflow in AppleBCMWLANCore Driver

#20
post #14

Earlier quoted context omitted.

Have they previously had an app transition like 32-bit / 64-bit, where some users cannot upgrade?

Nope, so this is going to be interesting to watch. Personally I was hoping that they would offer an optional download of 32bit support libraries to let iOS11 users run important existing legacy apps and access their documents, but they seem to push hard on making developers get in line and update their apps. Which is unhelpful for the cases where the developers no longer have any interest in their apps or even exist…

What was the point of that be? The apps aren’t going to be updated if they haven’t in the last four years. Keeping all that stuff around is also support burden for Apple.

If they only supported it on the 7 and below then it might be confusing to users why some people get to use older apps and others don’t. On the other hand if they wanted to support it on the 8 and X then they would have to have an entire processor emulator that would only exist to support apps that hadn’t been updated in years.

Don’t forget that Apple keeps tons of usage statistics from people who are willing to give them. Chances are they know pretty exactly what percent of people use 32 bit apps with any regularity and how much total time to use them for. If they were willing to make these decisions my guess is those numbers are very low.

People here on HN are concerned about it and there have been some articles on websites about it but I’m willing to bet that this whole thing is almost a non-issue.

Post reply on HN