AfterDawn: Tech news

Apple iOS 4.1 passcode security glitch revealed

Written by James Delahunty (Google+) @ 26 Oct 2010 11:32 User comments (6)

Apple iOS 4.1 passcode security glitch revealed A glitch in Apple's iOS 4.1 software that allows anyone access to potentially sensitive information has been revealed by iPhone owners online.
An easy trick allows anyone to bypass the passcode entry screen and gain access to the iPhone App. To do this, the user must select "Emergency Call" at the passcode screen, then input any number. Then hitting "Sent" and the iPhone sleep button in an _almost_ simultaneous succession will give the user full access to the iPhone app.

This means the user will have access to Contacts, Call History, Voicemail and Dialer. A few further tips include hitting "Share Contacts" and the camera button, which will get you access to the Photos app. It is also possible to send an e-mail or MMS with the device.

The loophole does not exist in the iOS 4.2 beta, which suggests that Apple is already aware of the flaw.

Previous Next  

6 user comments

126.10.2010 12:28
frankorizzo
Unverified new user

Why is this being reported as a "glitch"?!
It's a bug! Oh, I guess only MSFT has bugs, from
bad code but Apple only has little "glitches"
that are someone else's fault.

226.10.2010 14:13

I used to work for apple I feel sorry for my ex co workers who have to deal with crazy people calling in about something stupid like this



326.10.2010 14:13

I used to work for apple I feel sorry for my ex co workers who have to deal with crazy people calling in about something stupid like this



426.10.2010 15:36

Originally posted by frankorizzo:
Why is this being reported as a "glitch"?!
It's a bug! Oh, I guess only MSFT has bugs, from
bad code but Apple only has little "glitches"
that are someone else's fault.
LOL, good one. There is much less accountability at Apple, as evidenced by their treatment of the antenna issue.

526.10.2010 19:04

I saw this news yesterday, seems like apple just can't catch a break.

626.10.2010 23:04

No, they could have easily caught a break...they knew about the issue, patched it for the future release, and then did not release an update. They can catch a break, they just seem determined not to do it.

Comments have been disabled for this article.

News archive