Yesterday we reported that select Samsung handsets running its TouchWiz UI were affected by a flaw that could allow them to be remote wiped after clicking on a malicious link. Samsung has now confirmed it has patched the flaw for its flagship Galaxy SIII handset.
Samsung is urging Galaxy SIII owners to update to the latest version of its software to ensure they are protected against the flaw.
what are your opinions, ideas about this brothers? i wonder if sony will still provide us with a patch.. im using stock GB, downloaded the -- https://play.google.com/store/apps/d...onerootscanner and stated that my phone is not patched and is vulnerable..
here is the android security flaw im talking about if you dont know -- http://bluebox.com/corporate-blog/bl...id-master-key/
A security vulnerability that was discovered in the Linux kernel affecting the Ubuntu 10.04 LTS (Lucid Linx) operating system, was announced by Canonical.
This is the kernel vulnerability found in the Linux kernel packages: CVE-2012-2745. The system could be made to crash under certain conditions. A flaw was found in how the Linux kernel passed the replacement session keyring to a child process.
Google has patched a master key vulnerability in Android that was recently identified by Bluebox Security, according to an industry report. The vulnerability, which allowed hackers to modify APK code without breaking an apps cryptographic signature, could convert 99 percent of all Android apps into malicious Trojans, claimed Bluebox.
If you are reading this in Internet Explorer, you should probably close it and fire up Chrome -- and come back after a newly reported zero-day flaw is patched. Even the U.S. and U.K. governments are warning against use of Internet Explorer for now. The zero-day flaw has been uncovered in Internet Explorer versions 6,7, 8, 9, 10, and 11, according to Microsoft.
Remember that little vulnerability we heard about on Nexus devices that could be maliciously exploited to cause a device to lock up and reboot? Looks like Google has finally added a fix for that in Android 4.2.2, which should be rolling out fairly soon.