Apple has just released iPhone OS 3.0.1 via iTunes.
iPhone OS 3.0.1 fixes an SMS vulnerability.
Products compatible with this software update:
• iPhone
• iPhone 3G
• iPhone 3GS
MacDailyNews Note: The download, at least for the iPhone 3GS, weighs in at 297.9MB.
To get and install the update:
• Make sure you are using iTunes 8.2. Connect your iPhone to your computer.
• When iTunes opens, select your iPhone under Devices in the Source List on the left.
• In the iPhone Summary pane, click Check for Update.
• Click Download and Install. Do not disconnect your iPhone until the update has finished.
“This morning, less than 24 hours after a demonstration of this exploit, we’ve issued a free software update that eliminates the vulnerability from the iPhone,” said Tom Neumayr, an Apple spokesman, in a statement. He said “no one has been able to take control of the iPhone to gain access to personal information using this exploit.”
MacDailyNews Take: Boom, that was even quicker than expected!
[Thanks to MacDailyNews Reader “JMS in TX” for the heads up.]
sms hack fixed? Hopefully. I just got my first iPhone. I’m happy as a kid at Christmas!!
Don’t forget–If you’re jailbroken, wait for the Dev Team to clear the update!
300MB to fix a one byte issue. Well, at least it was fast.
did it break tethering?
as TowerTone said,
someone who is tethering test this out for us
” width=”19″ height=”19″ alt=”wink” style=”border:0;” />
Teathering still works!
Can anyone clarify. I’m assuming this isn’t the main 3.1 update we’re all expecting, rather, an SMS hack plug?
Awwwww, forget it. I just can’t read today, now can I?
What about the Touch battery issue fix????? and Wifi signal weakness fix???? WTF?
does this update fix any 3.0 bug fixes? my edge and 3G are much slower on 3.0….all around sluggishness. phone will freeze at times as well.
Wondering if this fixed both SMS and the Palm Pre work around…
Reading comprehension at an all time low.
“iPhone OS 3.0.1 fixes an SMS vulnerability.”
No 3.0 bug fixes, no battery issue fix, no wifi signal weakness fix, no “Palm Pre work around” (which would be in iTunes anyway).
And MDN’s take is debatable: only “quicker than expected” if you don’t expect Apple to take security threats all that seriously. Some of us would have hoped for a fix before the vulnerability was laid out in detail to the world.
Let the circus begin!
Hackers vs Jailbreakers- FIGHT!
This will be amusing. Everyone else will have protected their phones- only the JB’ers will be vulnerable to this. Of course they will come crying to Apple.
HILARIOUS.
Okay, no bug fixes. But now we have the important question:
Is it snappier?
Using a Beta Version of 3.1, I’m stuck with the vulnerability.
30% snappier.
John – Can you tell me how exactly Apple should have released this more quickly?
Thank you, John. I was beginning to wonder if anyone bothers to read the article before posting.
Anyone know if 2.2.1 is affected by the SMS vulnerability? I’ve been waiting for 3.1 before upgrading because of so many of the problems people have reported regarding 3.0.
John – Can you tell me how exactly Apple should have released this more quickly?
The researchers told Apple about this flaw, what, 6 weeks ago? Apple could have released this before the conference this week, rather than play chicken with the cracker community.
Well, this answers my question from this morning in a post in another article.
“no one has been able to take control of the iPhone to gain access to personal information using this exploit.”
I thought so, since I could find nothing about anyone witnessing the exploit extracting info from an iPhone at the BH conference.
My SMS feels snappier.
@ 2.2.1:
Just upgrade already! Geez . . .
O delicious irony!
Let the circus begin!
Hackeps vs Jailbreakers- FIGHT!
This will be amusing. Everyone else will have protected their phones- only the JB’ers will be vulnerable to this. Of course they will come crying to Apple.
Spoken like someone who truly has no idea what he’s talking about.
My guess is that Apple would have preferred to wait and incorporate this fix into it’s next real update (which would fix all the other problems) but the Black Hat thing pushed them to do this fix on it’s own.
Are we all supposed to thank the hacking folks now? Hmmm
As slow as Apple usually is with security updates, this problem must have really been considered a humdinger.