BTRY B 529th FA BN
Lifer
maybe it was an automatic ban?
I don't see why people are bending over backwards to defend Apple here. He told them about the exploit before he submitted the app, and even then they let his app through the approval process. Not only did he expose a flaw in iOS, but he also exposed a a flaw in the approval process. On top of it all his app was only malicious against himself (according to the story). Apple shouldn't have banned him, it's just bad PR and he was just trying to help them out. Now they look like a-holes for banning a developer who was trying to help them.
He told them about the exploit before he submitted the app, and even then they let his app through the approval process. Not only did he expose a flaw in iOS, but he also exposed a a flaw in the approval process. On top of it all his app was only malicious against himself (according to the story). Apple shouldn't have banned him, it's just bad PR and he was just trying to help them out. Now they look like a-holes for banning a developer who was trying to help them.
Miller discovered the bug several months ago when researching iOS 4.3. At the time, he was busy with other research, including discovering a way to hack laptop batteries. But by September, he had fully exploited the flaw and was able to get a proof-of-concept app, which took advantage of it, into the App Store. According to Miller, that app was downloaded by quite a few people before Apple pulled the app on Monday, though he said only his copy is configured to download code from his server.
Miller alerted Apple about the weakness three weeks ago.
11/07/2011 @ 2:38PM |41,610 views
I don't see why people are bending over backwards to defend Apple here. He told them about the exploit before he submitted the app, and even then they let his app through the approval process. Not only did he expose a flaw in iOS, but he also exposed a a flaw in the approval process. On top of it all his app was only malicious against himself (according to the story). Apple shouldn't have banned him, it's just bad PR and he was just trying to help them out. Now they look like a-holes for banning a developer who was trying to help them.
The 5.01 update is available today and it addresses battery life as well as this security issue. The OTA update is 40-55 MB depending on device.
OS 5.0.1 Software Update
CFNetwork
Available for: iOS 3.0 through 5.0 for iPhone 3GS, iPhone 4 and iPhone 4S, iOS 3.1 through 5.0 for iPod touch (3rd generation) and later, iOS 3.2 through 5.0 for iPad, iOS 4.3 through 5.0 for iPad 2
Impact: Visiting a maliciously crafted website may lead to the disclosure of sensitive information
Description: An issue existed in CFNetwork's handling of maliciously crafted URLs. When accessing a maliciously crafted HTTP or HTTPS URL, CFNetwork could navigate to an incorrect server.
CVE-ID
CVE-2011-3246 : Erling Ellingsen of Facebook
CoreGraphics
Available for: iOS 3.0 through 5.0 for iPhone 3GS, iPhone 4 and iPhone 4S, iOS 3.1 through 5.0 for iPod touch (3rd generation) and later, iOS 3.2 through 5.0 for iPad, iOS 4.3 through 5.0 for iPad 2
Impact: Viewing a document containing a maliciously crafted font may lead to arbitrary code execution
Description: Multiple memory corruption issues existed in FreeType, the most serious of which may lead to arbitrary code execution when processing a maliciously crafted font.
CVE-ID
CVE-2011-3439 : Apple
Data Security
Available for: iOS 3.0 through 5.0 for iPhone 3GS, iPhone 4 and iPhone 4S, iOS 3.1 through 5.0 for iPod touch (3rd generation) and later, iOS 3.2 through 5.0 for iPad, iOS 4.3 through 5.0 for iPad 2
Impact: An attacker with a privileged network position may intercept user credentials or other sensitive information
Description: Two certificate authorities in the list of trusted root certificates have independently issued intermediate certificates to DigiCert Malaysia. DigiCert Malaysia has issued certificates with weak keys that it is unable to revoke. An attacker with a privileged network position could intercept user credentials or other sensitive information intended for a site with a certificate issued by DigiCert Malaysia. This issue is addressed by configuring default system trust settings so that DigiCert Malaysia's certificates are not trusted. We would like to acknowledge Bruce Morton of Entrust, Inc. for reporting this issue.
Kernel
Available for: iOS 3.0 through 5.0 for iPhone 3GS, iPhone 4 and iPhone 4S, iOS 3.1 through 5.0 for iPod touch (3rd generation) and later, iOS 3.2 through 5.0 for iPad, iOS 4.3 through 5.0 for iPad 2
Impact: An application may execute unsigned code
Description: A logic error existed in the mmap system call's checking of valid flag combinations. This issue may lead to a bypass of codesigning checks. This issue does not affect devices running iOS prior to version 4.3.
CVE-ID
CVE-2011-3442 : Charlie Miller of Accuvant Labs
libinfo
Available for: iOS 3.0 through 5.0 for iPhone 3GS, iPhone 4 and iPhone 4S, iOS 3.1 through 5.0 for iPod touch (3rd generation) and later, iOS 3.2 through 5.0 for iPad, iOS 4.3 through 5.0 for iPad 2
Impact: Visiting a maliciously crafted website may lead to the disclosure of sensitive information
Description: An issue existed in libinfo's handling of DNS name lookups. When resolving a maliciously crafted hostname, libinfo could return an incorrect result.
CVE-ID
CVE-2011-3441 : Erling Ellingsen of Facebook, Per Johansson of Blocket AB
Passcode Lock
Available for: iOS 4.3 through 5.0 for iPad 2
Impact: A person with physical access to a locked iPad 2 may be able to access some of the user's data
Description: When a Smart Cover is opened while iPad 2 is confirming power off in the locked state, the iPad does not request a passcode. This allows some access to the iPad, but data protected by Data Protection is inaccessible and apps cannot be launched.
CVE-ID
CVE-2011-3440
How's that OP?
I think Apple handles issues decently. I think they get a lot of flak because they're Apple. I bet if antennagate happened to any other device no one would have cared or made such a big deal out of it.
I think a lot of companies are at fault for not fixing their issue in a prompt manner. I mean how long did it take Samsung to fix their GPS issue?
I just installed the iOS 5.0.1 update on my iPad from 4.3.2, and the experience thoroughly sucked.
First, I was told that I needed to update iTunes to 10.5. The update failed. I tried again, and it failed again. I then uninstalled iTunes, and tried installing it again. The installation failed AGAIN (some problem with the Apple update service). I had to manually remove iTunes directories and registry from my computer before it would re-install successfully.
After all that, I then tried downloading the iOS 5.0.1 update. The download failed half way through. So, I downloaded it again. This time, the iOS update worked, but the application restore locked up half way through. So, now I have an updated iPad with NO working third-party apps. I'm trying to clean up that mess now.
They should thank him? Really? He pointed out the flaw to them privately (good), but then, like a tool, put together an app and got it approved and then let it get put out there. I am not sure if he pulled the app or it apple did, but if it was the latter, then no, it wasn't a dick move to ban him.
If the story had been that he made an app, later discovered that it had this exploit, alerted apple, and pulled it then it would be a dick move to ban him.
So Apple allows apps on their store that exploit vulnerabilities? They're supposed to check all that stuff BEFORE allowing the apps.
First, I was told that I needed to update iTunes to 10.5. The update failed. I tried again, and it failed again.
So, now I have an updated iPad with NO working third-party apps. I'm trying to clean up that mess now.
So Apple allows apps on their store that exploit vulnerabilities? They're supposed to check all that stuff BEFORE allowing the apps.
So people cry when these apps make it through, but they cry anyway when Apple bans the dev. Either way it's lose lose for Apple because Phandroids will cry one way or the other.
Seriously, with threads like these, it's just a troll attempt. When your daily Android Propaganda man posts an article like this and talks about Apple fumbling it in the title, you know what to expect.
Honestly, if you look at it Apple's handled a lot of these issues better than say Samsung handled their GPS issues or the Froyo update for US SGS phones... or better than Motorola has handled the entire bootloader controversy.