iPhone, iPod Touch 1.1.1 Firmwares Jailbroken
vertigoCiel writes "Hackers Niacin and Dre have recently gained full read and write access to the filesystems of both the iPhone and the iPod Touch. The Jailbreak exploits a vulnerability in Safari's TIFF library to execute the necessary code when the specially crafted image is loaded. Access can then be permanently sustained by modifying the fstab file with iPhuc"
I wonder if Apple are going to keep playing "cat and mouse", and try to bring legal action to bear against these "vile hackers", or if they're going to take the hint that you can't stop us all? Clearly there's a demand for unlocked iPhones.
Seven puppies were harmed during the making of this post.
iphucing love the name
Apparently they used the same vulnerability to hack the PSP.
Wouldn't it be easier to buy an phone/mp3 player that isn't crippled?
Don't patch until there is a working hack for the new patch. And yes, a new hack will always surface.
Is there any place/website I can just go to and find out the "current status" of what I can do with specific firmware revision? Without digging through the developer forums, or idling in IRC asking stupid questions?
Sure, you can always come to slashdot to ask stupid questions. : p
They need to patch anyway.
:p
Every single iphone and touch is running a vulnerable safari (using a year out of date libtiff). Once the virus writers get hold of this then there'll be all sorts of stuff going on.
Of course the hacked phones will be immune as one of the first things that will be done is fix the bug.
according to the article since the TIFF exploit can be patched. I understand it's a "cat and mouse game", but I was wondering why there can't be a more permanent solution, like creating an image that can be restored using the iTunes Restore function.
This is great news and I'd like to know how do you get started learning how to hack the iPhone? I found stuff that explains how the jail breaking works, but not how it was discovered or what was tried, etc. Blogs, logs, etc would be cool.
I bet Sony and Apple both have an intern whose sole job it is to churn out new FW for the PSP and iPhone/Touches. Ocasionally they will slip in a few bug fixes and patches for security holes. Other than that they will end up releasing one update a week with the hackers always a week behind.
I have excellent Karma and I am not afraid to Troll it.
Am I the only person here who reads that there is a vulnerability in the way iPhone handles TIFF files who immediately thinks that this is a massive security problem that needs to be addressed immediately? Sure, a handful of people will make use of this to open up their iPhone. Good for you. However, for everyone else, this is just a hole waiting to be exploited by someone posting a malicious TIFF onto a website or in an email and luring the iPhone users to view the TIFF causing havoc.
Reposted from: http://www.iphonealley.com/news/iphone-v1-1-1-jailbreak-apptapp-installation-guide
.ipsw if it comes as a .zip ./iphuc and hit return
Jailbreaking Steps
1. Sync and pray
1. Sync your iPhone with iTunes. You'll be losing all of your information, so it's a good idea to back up
2. Downgrade to v1.0.2
1. Hold down the Sleep/Wake and Home buttons at the same time for about 10 seconds. The phone should shut down.
2. When the phone shuts down, release the Sleep/Wake button but continue holding Home
3. Wait until iTunes recognizes the iPhone. The screen will appear to be off, but iTunes will eventually recognize the iPhone. When it does, let go.
4. A message will appear telling you to restore. Click OK
5. Using your favorite browser, download the v1.0.2 software from this location. You may need to rename to
6. Back in iTunes, hold Option on the Mac or Shift on the PC while clicking Restore. Navigate to the software you downloaded and select it.
7. The phone will restore, but it will fail. This is normal.
8. Your iPhone should show a yellow triangle. Run Nullriver's AppTapp. It should bring you back to the Activation step on the phone and show an error in the application. Disregard the error.
9. Run AppTapp again and it should succeed.
10. If not using an AT&T SIM, use INdependence to activate your iPhone. That's it!
3. Create Symlink
1. If you haven't already, install Nullriver's AppTapp
2. Go to http://conceitedsoftware.com/iphone/beta in iPhone's Safari. Tap "Yes" to add to Installer
3. Plug iPhone in and open iTunes. Make sure it's recognized before proceeding
4. Using Installer, install "Trip1Prepz" located under "System"
4. Upgrade to v1.1.1
1. In iTunes click "Upgrade" and not Restore. Restoring will ruin our progress.
2. Once upgraded to 1.1.1, close iTunes
5. Jailbreak
1. Download iPHUC and friends from Rapidshare
2. Extract the contents so that iphuc, fstab, and iphonefs are all on the Desktop
3. If you don't have libreadline, download it and extract the zip to your Macintosh HD
4. Open Terminal.app located in Applications>Utilities
5. Type cd ~/Desktop and hit return
6. Type
7. Type getfile
Who said total nerds weren't funny? It's a wonder with comedy like this more pocket protector types don't get laid.
Well, according to the name of the program, at least one does...
This guy's the limit!
So let me get this straight: if an image handling vulnerability is in IE or Firefox, it's deplorable, but if it's in an iPhone, it's the greatest thing ever?
If you cretins don't like the iPhone's contract terms, DON'T BUY ONE.
Future versions are promised to include a camera as well. In the meantime one may connect an USB camera although it is not an elegant solution.
But a camera is not on the list of wanted features for me. I'll buy myself such Neo for Christmas (hope it'll be ready till then).
The people behind openmoco are really awesome - they were willing to give up WLAN because there were no chipsets with open drivers. Luckily they have found aetheros chipset afterwards, so 1973 will support wireless networking.
Such approach is very rare in the times of profit-at-all-cost companies. They have earned my respect by having principles.
In the Soviet Union the firmware is under legal obligation to maintain you for 5 years.
In South Korea only old people maintain their firmware.
I didn't know Apple had a sex-toy product line.
Apple's firmware division is not in charge of Gundam.
I didn't see anything that said otherwise, but doesn't this mean that someone could get root on your iPhone just by visiting a website with a special TIFF?
The problem is that they don't completely re-flash the firmware. If you have a 1.0.2 unlocked iPhone, the 1.1.1 upgrade will break your baseband and prevent you from making calls or using wi-fi. If they completely reflashed the baseband, that would not be an issue.
You are not part of Apple's target demographic for the iPhone. We can speculate on why, but it would just be speculation. It could be that AT&T demanded the phone be locked down. It could be that Apple rushed the phone out and didn't have time to add features allowing 3rd party applications while maintaining stability. It could be that they are all just a bunch of miserable pricks who wouldn't know a good business decision if it bit them in the ass.
The important thing is that you are not their target demographic. Getting angry at Apple for this is a bit irrational. Do you hate Nickelodeon for not producing good, quality porn? I mean, you supported them by watching their crappy Canadian-produced shows back when you were a kid.
W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
Otherwise, if you look closely at the specs and actually compare the units in your hand, you will find the iPhone to be a much "better featured phone" than the N95.
The N95 is clunky and poorly assembled, it has less battery life, less storage, and the apps it has are hardly useable and poorly integrated.
To really decide, try browsing the web on each phone. I will bet it will not be the N95 you choose.
If their hack depends on a "specially-crafted" TIFF, then that's a bug, and Apple is under an obligation to close that hole. How would you like it if a "specially-crafted TIFF" was used to steal all your personal information?
Open the SDK, Apple. Allow the legal unlocking, and make it easy for people to write apps and then sell them for them on iTunes. Stop being jerks. You make money to the extent that you're not jerks.
But hacking is hacking, and I don't want any vulnerabilities on my iPhone, even if it's just "good guys" who are using them.
Since we're moving more towards specifics that haven't been well-trodden, I'll start with the standard disclaimer: IANAL. Nor am I, by any stretch, an expert on the inner workings of the FCC.
Having said that, however, I have read through the final rules of 47 CFR Part 2, Cognitive Radio Technologies and Software Defined Radios, and I see nothing that would lead me to believe that an iPhone is any more subject to it than would be any other smart phone.
There are many smart phones, for instance, running the PalmOS or Windows CE that allow the user to load other applications without any hindrance at all. None of these appear to be in conflict with 47 CFR Part 2. So, this appears to me to fall under fear, uncertainty and doubt (FUD), rather than really being applicable. Whether specific control and access to the telephony components of the iPhone are via an OS X driver on the one hand, or via a PalmOS or Windows CE driver would appear to have no specific bearing. Likewise, it is not clear, by any means that the iPhone, or other smart phones fall under that rule.
I'm not trying to suggest that you're bringing up the possibility deliberately as fodder for FUD, just that it has some of the hallmarks: a general concern that sounds potentially problematic, whether it actually is or not, and not much in the way of detail other than that. I think it's legitimate to wonder whether or not 47 CFR Part 2 applies. But, I doubt that it really does. If it did, then I think there'd have been a significant brouhaha a long time since over one or another of the other smart phones that have already been out in the marketplace for a much longer time.
Note point two, from the Summary of the Memorandum and Order (my bold emphasis):
2. In the Cognitive Radio Report and Order, the Commission modified the rules to require that radios in which the software is designed or expected to be modified by a party other than the manufacturer be certified as software defined radios. To minimize the filing burden on manufacturers, this requirement was narrowly tailored to affect only those radios where the software can be modified by a party other than the manufacturer because such radios pose a higher risk of interference to authorized radio services. The definition of software defined radio (SDR) is intentionally broad, while the category of equipment that is required to be certified as SDRs is intentionally narrow. The Commission agrees with Cisco that a reading of the definition of SDR in the rules by itself may give the incorrect impression that more devices must be certified as SDRs than the rules intended to require. The Commission finds that the appropriate solution to Cisco's concern is to add an additional sentence following the definition of SDR to indicate the class of radios that must be certified as SDRs. It therefore clarifies the rules by adding the following statement to the definition of SDR: ``In accordance with Sec. 2.944 of this part, only radios in which the software is designed or expected to be modified by a party other than the manufacturer and would affect the listed operating parameters or circumstances under which the radio transmits must be certified as software defined radios.'' This action clarifies the intent of the rules adopted in the Cognitive Radio Report and Order.
Section 2.1 Terms and Definitions, subsection (c), defines 'software defined radio' as:
* * * * * (c) * * * Software defined radio. A radio that includes a transmitter in which the operating parameters of frequency range, modulation type or maximum output power (either radiated or conducted), or the circumstances under which the transmitter operates in accordance with Commission rules, can be altered by making a change in software without making any changes to hardware components that affect the radio frequency emissions. In accordance with Sec. 2.944 of this part, only radios in which
This just goes to show you that the more widespread and popular something is, the more likely it's going to get hacked (whether by the owner, or an outside party) to do something for which it was not originally intended. Mac owners who feel secure because they have Macs should take note of the fact that Apple's platforms do in fact contain exploitable flaws.
BeauHD. Worst editor since kdawson.
What's Apple's excuse for locking up the iPod Touch...?
With the iPhone it was apparently part of the contract they signed with AT&T, but with the iPod Touch, Apple has NO fucking excuse.