iPhone OS 3.1.3 Released

[ANDORYUU]

DO NOT UPDATE TO FIRMWARE 3.1.3 IF YOU ARE JAILBROKEN!

It is not safe yet to do so if you want to remained jailbroken and unlocked. This advice comes straight from the DevTeam via Twitter. If your silly enough to upgrade, I’ve got bad news…you can no longer restore to 3.1.2 unless you have your SHSH on file in cydia.

What's in this update:

Summary
This document describes the security content of iPhone OS 3.1.3 and iPhone OS 3.1.3 for iPod touch.

For the protection of our customers, Apple does not disclose, discuss, or confirm security issues until a full investigation has occurred and any necessary patches or releases are available. To learn more about Apple Product Security, see the Apple Product Security website.

For information about the Apple Product Security PGP Key, see "How to use the Apple Product Security PGP Key."

Where possible, CVE IDs are used to reference the vulnerabilities for further information.

To learn about other Security Updates, see "Apple Security Updates."

Products Affected
iPhone, Product Security, iPod touch
iPhone OS 3.1.3 and iPhone OS 3.1.3 for iPod touch
CoreAudio

CVE-ID: CVE-2010-0036

Available for: iPhone OS 1.0 through 3.1.2, iPhone OS for iPod touch 1.1 through 3.1.2

Impact: Playing a maliciously crafted mp4 audio file may lead to an unexpected application termination or arbitrary code execution

Description: A buffer overflow exists in the handling of mp4 audio files. Playing a maliciously crafted mp4 audio file may lead to an unexpected application termination or arbitrary code execution. This issue is addressed through improved bounds checking. Credit to Tobias Klein of trapkit.de for reporting this issue.

ImageIO

CVE-ID: CVE-2009-2285

Available for: iPhone OS 1.0 through 3.1.2, iPhone OS for iPod touch 1.1 through 3.1.2

Impact: Viewing a maliciously crafted TIFF image may lead to an unexpected application termination or arbitrary code execution

Description: A buffer underflow exists in ImageIO's handling of TIFF images. Viewing a maliciously crafted TIFF image may lead to an unexpected application termination or arbitrary code execution. This issue is addressed through improved bounds checking.

Recovery Mode

CVE-ID: CVE-2010-0038

Available for: iPhone OS 1.0 through 3.1.2, iPhone OS for iPod touch 1.1 through 3.1.2

Impact: A person with physical access to a locked device may be able to access the user's data

Description: A memory corruption issue exists in the handling of a certain USB control message. A person with physical access to the device could use this to bypass the passcode and access the user's data. This issue is addressed through improved handling of the USB control message.

WebKit

CVE-ID: CVE-2009-3384

Available for: iPhone OS 1.0 through 3.1.2, iPhone OS for iPod touch 1.1 through 3.1.2

Impact: Accessing a maliciously crafted FTP server could result in an unexpected application termination, information disclosure, or arbitrary code execution

Description: Multiple input validation issues exist in WebKit's handling of FTP directory listings. Accessing a maliciously crafted FTP server may lead to information disclosure, unexpected application termination, or execution of arbitrary code. This update addresses the issues through improved parsing of FTP directory listings. Credit to Michal Zalewski of Google Inc. for reporting these issues.

WebKit

CVE-ID: CVE-2009-2841

Available for: iPhone OS 1.0 through 3.1.2, iPhone OS for iPod touch 1.1 through 3.1.2

Impact: Mail may load remote audio and video content when remote image loading is disabled

Description: When WebKit encounters an HTML 5 Media Element pointing to an external resource, it does not issue a resource load callback to determine if the resource should be loaded. This may result in undesired requests to remote servers. As an example, the sender of an HTML-formatted email message could use this to determine that the message was read. This issue is addressed by generating resource load callbacks when WebKit encounters an HTML 5 Media Element.

 

[gdude30]

Oh please. They always say, "DO NOT UPGRADE IT WILL FUCK UP JAILBREAK OR YOU WILL NOT BE ABLE TO JAILBREAK"

A day later, "The Devteam has jailbroken *insert firmware here* and the download will be up in a few days. YAY PWNAGE"

But I don't think 3.1.3 does anything so I don't see any reason to upgrade anyways. But thanks for the warning. But I'm sure they'll crack it soon.

 

[navinator]

This time the "do not upgrade if you want to jailbreak" reasoning is actually for a purpose as opposed to giving the dev team time to test the jailbreak software and update if necessary - 3.1.3 fully patches the exploit that current jailbreak software uses.

 

[gdude30]

Well I believe that goes without saying with any new firmware.

While the it fully patches the exploit that they "currently" use that just means they'll find another way. They don't give up. At least not that I've seen.

But until there is any word of them moving close to finding a solution you are correct it would be wise not to upgrade if you plan on jailbreaking one day. But I still believe it's only a matter of time til they crack it.

 

[Jimboy121]

This is why i never jail breaked my iphone, it seems too much hassle, i am happpy with that i have on my iphone, i'm sure they will realise certain things in the future which you can currently do with a jail broken phone.

 

[navinator]

I've jailbroken my iPhone before, although it's now back on stock Apple software, as well as my iPod touch (which is currently still jailbroken). Once you get the hang of exactly what to do it's pretty easy and there are some neat things you can do. The main issue I had is when an update is released, like with going from 3.1.2 to 3.1.3, you end up back on the stock software and have to do everything over - it's basically a decision between keeping your jailbreak and everything you want or having to go back through and set everything up on the new software.

 

[just_mills]

Happily updated.

Fuck Jailbreaking..

 

[gdude30]

What this really applies to is I think the second generation touches and the 3GS. For some reason the 3G is not affected by this. The problem is that apple isn't signing the older firmware even more. So even though I have 3.1 in the past I could just make my own custom firmware and jailbreak with that. But now apple's servers aren't going to sign those anymore meaning they won't work.

However, there is something about if you've jailbroken before and backed it up using SSH or something than it's possible to jailbreak. I am not sure if it is true that 3G's aren't affected and if that's true why 3G's aren't affected by 3GS is. But I'll look into this. I've been thinking of jailbreaking again.