Samsung TouchWiz vulnerability will wipe some phones after just clicking a link

[Jodell88]

Samsung is finding itself in a spot of bother this morning, as a particular piece of HTML code has emerged that, when clicked, instantly resets the Galaxy S II — and potentially other Android devices running the TouchWiz UI. Posted by Pau Oliva earlier today, the code was initially thought to affect the current flagship Galaxy S III model, however multiple negative reports and our own testing have shown that it only brings up the phone's dialer, failing to execute the full reset without user intervention. The latter is really the issue here: Samsung's software changes atop stock Android are allowing the GS II to automatically dial the hard reset code, taking away a critical aspect of user control.

http://www.theverge.com/2012/9/25/3403928/samsung-touchwiz-reset-vulnerability

 

[Eug]

All the more reason for using a stock Nexus.

 

[jpeyton]

All the more reason to never click unknown links.

Fixed.

 

[ChAoTiCpInOy]

It's awesome how this is not getting anywhere near the amount of coverage/responses from here and the tech sphere.

 

[mikegg]

Fixed.

It's hard not to click on unknown links - especially how popular URL shorteners have gotten due to Twitter.

 

[Oyeve]

I thought this was fixed already. Anyway, dont click on unknown links. Same as with any gadget/computer.

 

[Bateluer]

I thought this was fixed already.

It was, on the OTAs that were pushed out weeks ago on all US carriers. News outlets and blogs jumped the gun, and most never bothered to update or retract their incorrect articles.

To reiterate, this exploit was fixed and does not work.

 

[Ravynmagi]

Of course never click on unknown links. But accidents do happen. A little in the browser and you tap on a different spot than you meant too, perhaps some close links and a fat finger, an accidental tap. Things happen with touch input on a phone screen.

 

[lothar]

It's awesome how this is not getting anywhere near the amount of coverage/responses from here and the tech sphere.

Why would it when the issue has already been fixed in OTA updates?
OTA updates are carrier updates. If the carriers already fixed it, then obviously Samsung already fixed it a long time ago.
And we all know how long it takes US carriers to approve of Android OTA updates...

*EDIT*
All the more reason to get a Nexus.
I'm sure this bug affects HTC phones as well.
Nexus phones never had this bug.

 

[jimhsu]

All the reason to ... have backups?

Stuff happens, deal with it. The point is to minimize damage.