A recent bug that has also been reported Apple's official discussions forums, has been creating a major problem with iPhone 4S devices. The bug has been reported to generate random Apple IDs on the iPhone 4S, every time users complete a software restore action using an iCloud backup. The seriousness of the issue can be measured by the fact that the vulnerability gives the users a chance to sneak into others' Apple IDs - IDs that do not potentially belong to them, and thus, can be compromised further for access.

As discussed on Apple's forum, one user has claimed that Apple is working on a patch to this bug, while the actual emergence of such a bug dates back from day even before the seeding of the iOS 5.0.1, as mentioned in other threads on the same Apple forums.  Our blogging comrades at Electronista have come up with an exclusive video, capturing the situation stated. As demonstrated in the video embedded below, a notification pop up appears inviting the user to sing in through their Apple ID, but as a matter of surprise, the consequent Apple ID generated neither belongs to the iPhone 4S user, nor is the generated ID any of the other email addresses that the user uses on his iPhone 4S. The issues seems to persist, after disappearing for about 20 minutes or so, once each notification has been dismissed by the user, that too at the expense of generating six or seven random Apple IDs. The issue lives on even after all applications have been shut down.

The Fix

Well, there's a little temporary fix that has been suggested and perhaps the only one, which is to not use iCloud for restoring a user's device, and as an alternate, re-install iOS 5, in order to consequently restore from your desktop (Mac/PC) using iTunes. Apparently, the issue may widely involve any iOS devices that run iOS 5 and run iCould's restore capability, and not just iPhone 4S devices.

Let's hope Apple comes up with a quick fix for this vulnerability or else, the bug could be exploited at a much worse level to cause serious security breaches.

The original post was published on Simon Blog