Awfully nice of them to let Apple know what to patch next.
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU like Mac OS X; en) AppleWebKit/420+ (KHTML, like Gecko) Version/3.0 Mobile/1C28 Safari/419.3)
I don't think hackers will win this one. Apple has 1.1.2 ready to go as soon as 1.1.1 is hacked
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU like Mac OS X; en) AppleWebKit/420+ (KHTML, like Gecko) Version/3.0 Mobile/1C28 Safari/419.3)
I don't think hackers will win this one. Apple has 1.1.2 ready to go as soon as 1.1.1 is hacked
Basically, opening a carefully crafted TIFF image will crash mobile safari, causing a buffer overflow and allow for arbitrary code execution. This same exploit was used more than 1.5 years ago to crack the PSP firmware.
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU like Mac OS X; en) AppleWebKit/420+ (KHTML, like Gecko) Version/3.0 Mobile/1C28 Safari/419.3)
I don't think hackers will win this one. Apple has 1.1.2 ready to go as soon as 1.1.1 is hacked
Awfully nice of them to let Apple know what to patch next.
So a year ago when this issue was brought to light and they didn't fix it....... you think they'll do it NOW all of a sudden, eh?
Unfortunately, yup. A security related problem that affects the phone? When people started commenting on that the ringtone "trick" will be "fixed" in an update, I laughed it off. When the metadata/ringtone trick worked, they said it again. I poo-pooed. Each fixed, one update later. Arguably Apple's biggest mistake was leaving the phone so wide open. People are widely reporting the nature of this exploit. The only thing that will hold back a fix, will be the other fixes they want to include with it. Considering the Leopard launch, there will likely be an October iPhone update or a November iPhone update.So a year ago when this issue was brought to light and they didn't fix it....... you think they'll do it NOW all of a sudden, eh?