BadKernel Vulnerability Affects One In 16 Android Smartphones (softpedia.com)
An anonymous reader writes from a report via Softpedia: A security bug in Google's V8 JavaScript engine is indirectly affecting around one in 16 Android devices, impacting smartphone models from all major vendors, such as LG, Samsung, Motorola, and Huawei. Despite this bug being public for more than a year, only in August 2016 have Chinese security researchers discovered that the V8 issue also affected a whole range of Android-related products where the older V8 engine versions had been deployed. Affected products included Google Chrome Mobile, Opera Mobile, apps that use the WebView component (Gmail, Facebook, Twitter, WeChat, etc.) and apps that deploy the Tencent X5.SDK (a bunch of Chinese apps). It is estimated that around one in 16 Android devices is vulnerable to this issue, nicknamed BadKernel. The flaw leads to a RCE on Android devices, allowing attackers to take full control over one's smartphone. Despite BadKernel being discovered in August 2016, because all research was only published in Chinese, most E.U. and U.S. users have no clue they might be affected. One of the best ways to protect yourself, as noted in the report, is to keep your apps and operating system updated. You can view this list via Trustlook's website to see if your device is affected. There's also a dedicated BadKernel security scanner you can download from the Play Store to check for the vulnerability.
At least they have a headphone jack, so no problem.
The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
A slashvertisment for a 'security' app that ostensibly tests for a vulnerability, whilst simultaneously asking for every permission my phone has. No thanks. And have a mode finger while you're here.
Silence is a state of mime.
For the common person, who relies on his carrier to publish updates; this is pointless. Even to that extent, if you jailbreak your device to patch it yourself, if you use said device in a managed-corporate environment, then it gets flagged as being non-compliant by MDMs and your device will no longer have access to corporate resources; if said policy is enforced.
One of the best ways to protect yourself, as noted in the report, is to keep your apps and operating system updated.
So how many of the devices listed are basically unsupported since initial sale and will never be update?.
I really wonder if things like this should be treated as manufacturing defects and since carriers and phone vendors don't seem to want to support these devices people should start bringing them back and getting them replaced for free as they are obviously defective.
I don't know warranty law but maybe someone one could chime in who has some idea as it would seem that if these issues aren't fixed then the customer is due a replacement or refund because their device does have a manufacturing or design defect.
Time to offend someone
I guess my phone is safe.
"Install this piece of random software to see if you're safe from this vulnerability that affects a ton of devices."
Yeah, right. It's precisely that mentality that causes more problems in the first place.
My phone and tablet were both listed so I installed the app and ran the check and neither one was vulnerable to this bug. I don't think the list they have includes vendor OTA updates so its more less based on the software the devices had when they were stock. So my take away is don't put too much faith in that list by itself. You are better to do the check and then remove the app.
I read TFA and did a bit of Googling, but nowhere did I find any link to an actual technical description of the flaw. I'm interested to see how a kernel bug and a JIT bug work together here.
Wait. I thought this was an Android bug.
Could this bug be used, not to do devilish things, but to help me rooting my devices in a simple way, so that afterwards I could at least install the firewalls I already have on my old Fairphone*?
(*) that came pre-rooted by default, contrary to the new ones
Herve S.
"One of the best ways to protect yourself, as noted in the report, is to keep your apps and operating system updated."
That sounds great but when your vendor ships the phone with an already out of date OS and never releases any updates or patches after the sale, and your phone has little support in the jailbreak community... what are you to do?
I have never had a headphone jack fail. Nor do I know anyone who has.
I have. I am not claiming the following failure is common. I'm merely debunking the notion that the headphone jack is immune from problems. My personal experience is that it is the one and only thing that has failed for me in seven years.
I've occasionally dropped my phone, maybe once or twice a year over the last seven years. I only suffered damage once about five years ago. The headphone jack would no longer correctly detect when the earbuds were plugged in. Occasionally there would be a false positive where the phone erroneously thought the earbuds were plugged in and the phone would disable the speaker. I had to power down the phone to correct this. It was necessary to take this corrective action about once or twice a day. A day where this did not occur was rare. The problem was mechanical. If I shook the phone and listened very carefully I could hear something loose rattling. Fortunately this happened about three months before I became eligible for an upgrade.
If I were to purchase a Maytag dryer from Sears and know the warranty is good for one year.
New phones are shipping with older versions of Android. "New" as in unused, not as in a recent design.
I can get a new prepaid Samsung Galaxy S5 running Android 4.4 KitKat at Walmart for $150. It will not receive any updates to a newer version of Android. Some Android phones are vulnerable and have no upgrade path when they are new in the box, its not merely a problem of old used phones no longer being supported.
An S5? Not an ON5? I *just* went phone shopping and settled on a refurbed S5 for $120 shipped. All the Galaxy phones I saw in stores and online at that price were ON5s. I'd have gladly bought from WalMart at $150!
Defending IP by destroying access to it? That makes sense, RIAA/MPAA. Go to the corner until you can play nice!
My bad, that was a Galaxy S4 at $150, 4.2 Jellybean and not upgradable. Their S5 was $300, 4.4 KitKat and not upgradable.
I apologize for the confusion.
I work for Trustlook, so I am somewhat familiar with the company. :^)
Trustlook is a venture-funded Silicon Valley startup specializing in Android security. The company has an Android app in the Play store with over 18M users, plus a RESTful cloud SDK to enable virus scan capability in any Android app. We also have an analytic tool that allows you to peek inside any Android app (skyeye.trustlook.com). Finally, at the end of 2016, we will become the default security engine of every new phone for a top 3 phone maker, so we are not a fly-by-night company. But enough about Trustlook.
We have spent about a month collecting data from our user base to perform this research. Unlike many flimsy data studies out there, this one is based on 45K responses. Since Slashdot readers are naturally skeptical and highly inquisitive, we are making the detail report available here (goo.gl/9TBD8A). Judge for yourself if the research findings are worthy of our time.
Cheers,
- Clark Dong