Samsung's TouchWiz vulnerable to one-click data wipe or reset attack (video)
Share:
Share:
26 Comments
1. md227a posted on 25 Sep 2012, 07:51 15 1
Glad my S3 isn't running touchwiz! That would suck haha
12. dexter_jdr posted on 25 Sep 2012, 10:52 4 5
S3 still got OWNED!!! watch the last minutes of the video, the S3 got attacked by nfc...woohoo!!!
18. adelta90 posted on 25 Sep 2012, 14:33 2 0
yeah guess the S3 did get owned
but lets face it, unless someone deliberately tries to do this, its not likely for it to happen
At least this is something that can be corrected quite easily, but lets see if it does get corrected
23. PapaSmurf posted on 25 Sep 2012, 20:16 1 0
Chances of you receiving that through NFC?
0.000257812%.
26. brar.arsh posted on 26 Sep 2012, 03:16 0 0
Thanks To CM10 team that I am not on TouchWiz for my S3.. :D
2. neutralguy posted on 25 Sep 2012, 07:54 8 3
A good thing is, there's tons of solution for this. Change a ROM if you want to :)
8. JonBjSig posted on 25 Sep 2012, 10:04 1 0
You can also just download a different dialer, then you'll be prompted first.
4. kamil posted on 25 Sep 2012, 08:20 6 2
touchwiz UI is the most boringest (if there is word for that) UI you can ever get on an Android platform device literally.
11. Berzerk000 posted on 25 Sep 2012, 10:49 3 1
Another reason added to my list of why Touchwiz is not to be trusted.
17. EclipseGSX posted on 25 Sep 2012, 13:51 4 2
I love HTC Sense. Back in the day I preferred my OG EVO over the SGSII even though the screen was beautiful it still felt like a downgrade going to Touchwiz
14. taz89 posted on 25 Sep 2012, 11:46 0 0
Does this affect everyone or just US PHONES... verge reports they only got it to work on a at&t s3...either way let's hope this is fixed ASAP and should not be a problem unless you or on dodgy sites
15. tedkord posted on 25 Sep 2012, 13:05 0 0
Come on, Samsung. Address this. It should be as easy as having a confirm factory reset dialog box poo up for all hidden code disks.
16. Gingershnaps posted on 25 Sep 2012, 13:41 5 0
Per another android site:
Update: This issue is, unsurprisingly, a lot more nuanced than the video here lets on. The bug is based in the stock Android browser, is in fact quite old, and has been patched in more recent builds of Android - this is probably why Nexus devices running the most recent OTAs are unaffected. The fact is, this is not a Samsung problem, it's an old Android problem that has been known about for some time.
Any of the U.S. SGs3 that have their OTA updates aren't able to be affected.
19. christianqwerty posted on 25 Sep 2012, 15:34 2 0
touchwiz has crashed on my s3 so many times
22. tedkord posted on 25 Sep 2012, 19:51 1 0
Really? I don't think I've had TouchWIZ crash even once in the two months I've had my GS3. And I tinker a lot.
24. PapaSmurf posted on 25 Sep 2012, 20:19 0 0
^ This.
And I've managed to reach 1.56GB of RAM of 1.59 and it didn't crash or lag, at all.
20. Martine posted on 25 Sep 2012, 16:32 0 0
@ Phonearena.
This has been confirmed to be a vulnerability of the stock Android browser. A fix for this hack was released with the latest Jelly bean update.
Therefore, the hack will affect any android device running previous versions of Android.
You can use a simple google search to confirm this info.
Please update the post.
Thanks.
Jokesy
21. geesanut posted on 25 Sep 2012, 16:49 0 1
Looks like a conspiracy to me.? (LoL)! Phones not meeting expectations,android haters, could it be possible!?


