3 ms·
Which device? That doesn't sound right. We're in a more or less identical situation, with Galaxy Tab S2's for the kids that we bought three years ago. And in
by ajross 7y ago
Which device? That doesn't sound right. We're in a more or less identical situation, with Galaxy Tab S2's for the kids that we bought three years ago. And indeed, they're running comparatively ancient Android 7.0 images and will never see a version bump again.
They do, however, continue to see security updates. And in particular they've been patched against the vulnerability in the linked article. I'd be very surprised if yours was any different.
- nolok 7y agoHe's probably wrong, but inadvertently so. Most people seem to confuse android version update with security update, which is compounded by the fact that security updates on android are very "discreet" all things considered, and you don't notice it much.
- Angostura 7y agoI'll have a check in a couple of hours and and report back. The Device, bought in September 2016 was a Samsung Galaxy TAB E 9.6 SM-T560 WI-FI
- pmlnr 7y ago> comparatively ancient Android 7.0 7.0 is ancient? 5.1, or rather 4.4 is ancient.
- TeMPOraL 7y agoAndroid with a version number is ancient; current Androids have single letters in their name.
- deleted 7y ago[deleted]
- Santosh83 7y agoThe Android ver on my phone is 4.1. Still runs just fine, but then again all I use it for are calls/SMS, so there's little scope to be exploited.
- CannisterFlux 7y agoIt might still be vulnerable to stagefright, exploitable over MMS.
- ajross 7y agoStagefright is the name of the component, not the exploit. And in most cases, devices from major vendors are going to have patched binaries, even on images as old as Jellybean.
- sangnoir 7y ago> ...all I use it for are calls/SMS, so there's little scope to be exploited. You mean little scope of exfiltration (I'm guessing it's not connected to the internet). There are a lot of vulnerabilities in text rendering that can be exploited via SMS.