Never miss an update Follow AppleInsider
Friday, February 15, 2013, 09:42 am
Apple to release iOS 6.1.2 to address passcode vulnerability by February 20 -report
Apple is already working on an update to iOS 6 to address a dangerous passcode vulnerability discovered earlier in the week, with one report claiming that the company anticipated issuing the update as early as next week.German blog iFun published the latest information on the fix Friday, saying that iOS 6.1.2 will arrive early next week, and likely before February 20. iFun accurately predicted the launch of iOS 6.1.1, relying on the same sources that tell them 6.1.2 is on the way.
News of the lockscreen exploit hit the Internet Wednesday. Using the bypass method, one can view and modify an iPhone owner's contacts, listen to voicemail, and browse through their photos. The exploit does not, though, appear to grant access to email or the web.
Apple on Thursday acknowledged the vulnerability. The company, representatives said to the media, is hard at work on a patch, though they provided no hard details on when users could expect one.
On Topic: iPhone
- AT&T to bring FaceTime over cellular to all customers by end of year
- Apple debuts new iPhone discounts, subsidies to gain ground in India
- Looking to pull even with Apple, Samsung to pay developers for Galaxy-specific apps
- 10M Samsung flagship phones in 28 days a 'record,' 5M iPhone 5 in 3 days 'disappointing'
- Briefly: Virgin Mobile offers 15% discount on prepaid iPhone 4/4S
Previous Comments View All
Ugh. Shouldn't have gone out with this bug. Doesn't speak well to Apple's QA process. This usage case is too common not to undergo testing. Somebody should get smacked for this.
Have you read the article? the things you have to do to reproduce this so called "bug" are insane. Apple of course has to jump on it to keep the media circus at bay.
Looking forward to iOS 6.1.3.
Ugh. Shouldn't have gone out with this bug. Doesn't speak well to Apple's QA process. This usage case is too common not to undergo testing. Somebody should get smacked for this.
"This would never happen if Steve were alive..."
"Now we know what happened to the MobileMe team..."
"Tim Cook is failing, there's been no innovation since he took over..."
"This is the beginning of the end for Apple..."
"It's the 1980s all over again..."
"iOS isn't exciting..."
"I love Apple, but it seems like they're making more mistakes..."
/s
Have you read the article? the things you have to do to reproduce this so called "bug" are insane.
Not really. Clearly it would be difficult to find if you were unaware of the bug, but once you know the procedure (e.g. when it's all over the internet) it's fairly easy to exploit.
I hope the Exchange issue is resolved as well. Not going to point fingers here. Just want this to be fixed.
Apple says: http://support.apple.com/kb/TS4532
Microsoft says: http://support.microsoft.com/kb/2814847
Not really. Clearly it would be difficult to find if you were unaware of the bug, but once you know the procedure (e.g. when it's all over the internet) it's fairly easy to exploit.
See, that wasn't the point. He's claiming it's Apple's fault, when there is no reasonable expectation for them to ever have known about something like this.
A five day turnaround on a bug that isn't even a serious security issue is absolutely amazing. Nothing to criticise here at all.
Conspiracy theory:
Someone at Apple discovered this bug a while ago and kept it on hold until the jailbreak came out. This way Apple can release a fix for both and no one can say that Apple turned off the jailbreak on purpose because they have a perfect cover for the releasing an early fix. 
Ugh. Shouldn't have gone out with this bug. Doesn't speak well to Apple's QA process. This usage case is too common not to undergo testing. Somebody should get smacked for this.
This should be fixed no doubt but i wouldn't say this is even a remotely common use case. You have to execute a fairly large number of steps in a proper sequence to even have a chance of this happening. Plus someone would have to have physical access to your phone and have the knowledge to even attempt this. It is a vulnerability that is being addressed, but I doubt that anyone was adversely effected by this. At least until these tech sites and that idiot on You Tube showed everyone how to do this
See, that wasn't the point. He's claiming it's Apple's fault, when there is no reasonable expectation for them to ever have known about something like this.
I've heard that Apple was directly responsible for the Russian bolide this morning also. 
Latest Apple Headlines
-
AT&T waives voice, data and text overage fees for Oklahoma tornado victims
~3 hours ago -
Briefly: South Australia's first Apple Store to open Saturday in Adelaide
~8 hours ago -
Facebook's Share Dialog for connected iOS apps promises enhanced usability, easy coding
~9 hours ago -
Yahoo announces 1TB Flickr accounts, new UI with high-resolution photos
~11 hours ago -
Apple created offshore subsidiaries to avoid paying billions in US taxes, Senate panel says
~11 hours ago - more...
| Model | White | Black | |
|---|---|---|---|
| iPad mini (WiFi only) | |||
| 16GB WiFi |  |
$329.99 | $329.99 |
| 32GB WiFi | |
$429.99 | $429.99 |
| 64GB WiFi | |
$529.99 | $529.99 |
| iPad mini (WiFi + 4G) | |||
 |
 |
 |
|
| 16GB 4G White | $459.99 | $459.99 | $459.99 |
| 32GB 4G White | $559.99 | $559.99 | $559.99 |
| 64GB 4G White | $659.99 | $659.99 | $659.99 |
| 16GB 4G Black | $459.99 | $459.99 | $459.99 |
| 32GB 4G Black | $559.99 | $559.99 | $559.99 |
| 64GB 4G Black | $659.99 | $659.99 | $659.99 |
Lowest Prices Anywhere!
| Model | Price | You Save |
|---|---|---|
| Core i5 MacBook Pros w/ Retina | ||
| 13" 2.5GHz/8GB/128GB | $1,406.48 | $292.52 |
| 13" 2.5GHz/8GB/256GB | $1,479.99 | $519.01 |
| 13" 2.5GHz/8GB/512GB | $1,699.99 | $799.01 |
| Core i7 MacBook Pros w/ Retina | ||
| 13" 2.9GHz/8GB/256GB | $1,599.99 | $599.01 |
| 13" 2.9GHz/8GB/512GB | $1,799.99 | $899.01 |
| 15" 2.3GHz/8GB/256GB | $1,899.99 | $299.01 |
| 15" 2.6GHz/8GB/512GB | $2,299.99 | $568.01 |
| 15" 2.7GHz/16GB/768GB | $2,699.99 | $499.01 |
Ugh. Shouldn't have gone out with this bug. Doesn't speak well to Apple's QA process. This usage case is too common not to undergo testing. Somebody should get smacked for this.