7 ms·
iOS 7 Bug Lets Anyone Make Calls From Locked iPhones
- guilhermetk 13y agoJust tested it and It really allows me to make calls even with the phone locked.
- taspeotis 13y agoTested it as well. Extremely easy to exploit.
- untog 13y agoiOS7 definitely feels rushed. I work doing a lot of mobile web stuff, and the number of bugs in Safari in iOS7 is staggering. Here's hoping we see 7.1 very soon.
- chmars 13y agoIsn't iOS 7.0.1 more likely?
- Terretta 13y agoiOS 7.0.1 shipped yesterday.
- mikeash 13y agoSo about 100% likely!
- JohnTHaller 13y agoRight, but iOS 7.0.1 is just fixing the critical bugs that should have been caught before release. It'll take more like a point version to fix all the bugs in Mobile Safari: http://www.mobilexweb.com/blog/safari-ios7-html5-problems-apis-review http://www.mobilexweb.com/blog/safari-ios7-html5-problems-ap... It's not like iOS users can install an alternate browser, either.
- rflrob 13y agoYes they can: https://itunes.apple.com/us/app/chrome/id535886823?mt=8 https://itunes.apple.com/us/app/chrome/id535886823?mt=8 https://itunes.apple.com/us/app/opera-mini-web-browser/id363729560?mt=8 https://itunes.apple.com/us/app/opera-mini-web-browser/id363...
- lttlrck 13y agoThey use the same renderer...
- JohnTHaller 13y agoEvery time the fact of Apple not permitting other browsers is brought up, someone always says "Yes they can" and points out Chrome, Opera, etc. But they can't. Apple won't allow any code interpretation in apps. That means no JavaScript at all. Which means a browser that's pointless on today's internet. Opera Mini isn't a true browser and offloads processing to external servers because they can't interpret JavaScript locally (thanks to Apple's anti-competitive app store rules). The off-device rendering makes for a less-than-desirable user experience. Chrome and every other "browser" in the iOS app store is just a custom UI on top of Mobile Safari. And it's not even full-speed instance of it since it can't use the Nitro JavaScript engine. It's hobbled so it's slower than proper Mobile Safari. Chrome does add one other custom bit in that it inserts its own network stack underneath it. But it's still Mobile Safari within Chrome. It's not the Chrome/Blink engine and it likely never will be. Not unless those increasingly high walls start coming down.
- joeblau 13y agoWhile I agree, they did pretty much redo everything on the UI while adding a bunch of features on the backend. They might have some more tricks up their sleeve later as well.
- seivan 13y agoNot to mention a HUGE API diff, with several new (and good) Frameworks. UIKit Dynamics is pretty cool, and so is Sprite Kit. Two of my favourites. They are not getting enough credit for that.
- joeblau 13y agoYeah. They deprecated almost the entire Game Center library. I was working on a game and when I update to iOS7 I got tons of warnings. There is still more stuff that I need to update, but I'll do it later. They aren't getting credit though because unless you're a developer, no one really cares. Most people want to see changes that effect them directly. That is something that I think Steve had a very good understanding of.
- seivan 13y agoMay I recommend https://github.com/seivan/SHGameCenter https://github.com/seivan/SHGameCenter
- partyanimal 13y agogive it time, iOS 7 has been out for just a couple of days. Android's been out for 5 yrs and it still feels rushed. ;)
- jamesmoss 13y agoWhy does responsible disclosure go out the window when it comes to iOS lock screen issues?
- untog 13y agoProbably because Apple has never acknowledged a problem with their platform, let alone rewarded one. Apple's outreach to any kind of dev community is nothing short of awful.
- tomrod 13y agoDoes that change ethical responsibility?
- cowsandmilk 13y agoI guess the official statement from Apple that they're working on the lock screen bugs is a case of "Apple never acknowledging a problem with their platform"? I guess they don't have a security-announce list where they post many bugs a month[1]. I guess the message to go along with iOS 7 that lists a bunch of security researchers who disclosed bugs to apple shows their awful relationship with developers[2]. What a bunch of FUD. [1] http://lists.apple.com/archives/security-announce/2013/Sep/index.html http://lists.apple.com/archives/security-announce/2013/Sep/i... [2] http://lists.apple.com/archives/security-announce/2013/Sep/msg00006.html http://lists.apple.com/archives/security-announce/2013/Sep/m...
- wmeredith 13y agoNow, now. We wouldn't want to let a pesky thing like reality get in the way of the Apple-hates-developers circle-jerk, would we?
- coldtea 13y agoReally? For all these years I follow such things, nothing you said it's true. Apple regularly posts security updates and notices, and they aknowledge the people who find them. Heck, even besides security, the claim that "Apple has never acknowledged a problem with their platform" is totally BS. Steve Jobs himself apologized for the iPhone 4 antenna, and there was also a public statement from Apple about iOS Maps. An of course, they also have the usual recall programs, for things such as faulty batteries, HD and such. So, FUD much?
- denzil_correa 13y agoI tried it on my phone and it indeed works.
- wiznvKNGNR 13y agoPerhaps this is a "feature" and not a bug. News like this just makes me want to go back to using "dumb" phones. adjusts tin-foil hat Apple knows what they're doing.
- sgt 13y agoI showed this to my girlfriend and she thought it was a feature - seeing that if you /really/ need to phone someone, why not allow this in Emergency Mode, as it's probably an emergency anyway? Yeah, I am not sure about that logic.
- frou_dh 13y agoThere seem to have been several lock screen bypass bugs over the years. Given that, you'd think they'd give it a hammering and find this stuff.
- chrisdevereux 13y agoI'm sure I'm missing something, but given how many there have been wouldn't you at least stick an `assert(!isPhoneLocked())` or similar on entry to anything that shouldn't be accessible while locked?
- testbro 13y agoIIRC most of these bugs arise because of things that should be available while the device is unlocked: the dialler and camera for example. Camera is supposed to restrict gallery access and the dialler is supposed to only permit emergency calls. I'd expect that every app trusted with running while the device is locked will have these bugs as Apple goes forward too. The bugs seem to a bit more nuanced than just testing for a locked device; the attacks seem to rely on performing actions simultaneously to exploit race conditions much like weird glitches in games. This class of bugs is really hard to test for due to the large search space. Model checking might offer a solution, but it's not a magic bullet by any means.
- frou_dh 13y agoSpeaking of games, that's exactly what the humble games tester spends a good chunk of time doing: uncovering bugs by coming up with weird things to try, like spamming input at unexpected moments.
- pearjuice 13y agoWith this in mind lock screens should be advertised as screensavers with passwords instead of actual lock screens; screens you tend to trust to protect your phone at all cost. Not screens which you can't be 100% certain of they actually lock your screen.
- bennesvig 13y agoWas this fixed in 7.0.1?
- RexRollman 13y agoI believe 7.0.1 fixed a fingerprint issue with the iPhone 5s.
- alexfringes 13y agoFor what it's worth, I'm unable to replicate this on a 5s running 7.0.1.
- josteink 13y agoAs usual with Apple, eye-candy is much more important than security. Their BSD foundation is pretty good, and then everything they add on top of it, pretty shoddy as far as security goes. I'm guessing Gruber and the rest of the Apple-crowd is not going to try to spin this one as vividly as they would have done, had this been an Android-exploit.
- lttlrck 13y ago'As usual'?!?!
- auctiontheory 13y ago... the company has focused too many of its resources on adding new features to handsets, and not enough ensuring that their basic functions work. Couldn't have said it better. Crazy that we're only now getting number blocking. (Okay, that's a "new feature," but it's a pretty basic one.)
- throwaway6781 13y agoThere is no excuse for not having a fuzz-testing framework to catch issues like this. It's straight-up lazy.