News for hackers. Stuff that matters.
Re:Remotely Compromising Android and iOS via a bug in Broadc... by ben1040 on Wednesday July 26, 2017 @05:18PM (#14860468)
This page has a table of OEMs/devices that, as of the end of May, were fewer than 60 days behind on patches.

https://android-developers.googleblog.com/2017/06/2017-andro...

To me, the takeaway from this is that unless you are using a "flagship" device, or one sold directly by Google, you're probably not getting updates in a timely manner.

Re:Remotely Compromising Android and iOS via a bug in Broadc... by thrownblown on Wednesday July 26, 2017 @05:57PM (#14860737)
Manufacturer: Device(S)

BlackBerry: PRIV

Fujitsu: F-01J

General Mobile: GM5 Plus d, GM5 Plus, General Mobile 4G Dual,

General Mobile 4G

Gionee A1

Google: Pixel XL, Pixel, Nexus 6P, Nexus 6, Nexus 5X, Nexus 9

LGE: LG G6, V20, Stylo 2 V, GPAD 7.0 LTE

Motorola: Moto Z, Moto Z Droid

Oppo: CPH1613, CPH1605

Samsung: Galaxy S8+, Galaxy S8, Galaxy S7, Galaxy S7 Edge, Galaxy S7 Active, Galaxy S6 Active, Galaxy S5 Dual SIM, Galaxy C9 Pro, Galaxy C7, Galaxy J7, Galaxy On7 Pro, Galaxy J2, Galaxy A8, Galaxy Tab S2 9.7

Sharp: Android One S1, 507SH

Sony: Xperia XA1, Xperia X

Vivo: Vivo 1609, Vivo 1601, Vivo Y55

Re:Remotely Compromising Android and iOS via a bug in Broadc... by feikname on Wednesday July 26, 2017 @09:25PM (#14861922)
Just a disclaimer, this isn't the complete list of devices that received the July 2017 update. I, for one, received it for my Moto G4 Play in Brazil.

This list shows the models with a MAJORITY OF DEPLOYED DEVICES running a security update from the last two months.

Re:Remotely Compromising Android and iOS via a bug in Broadc... by thrownblown on Wednesday July 26, 2017 @09:50PM (#14862024)
Yeah I just cut and pasted from the link above
Re:Remotely Compromising Android and iOS via a bug in Broadc... by JepZ on Wednesday July 26, 2017 @07:49PM (#14861434)
And yet another time we learn why it is better to use Lineage OS. Five year old Samsung S3:

  Android: Version 7.1.2
  Security Patch Level: 5th July 2017
Re:Remotely Compromising Android and iOS via a bug in Broadc... by ihattendorf on Thursday July 27, 2017 @02:20PM (#14867992)
Note that not all vulnerabilities are/can be patched by LineageOS, regardless of what the security patch level claims. Your device maintainer needs to actively merge patches into the kernel/device (see [0], note that this list relies on maintainers to update it). In addition, binary blob firmware needs to be patched by the manufacturer (e.g. Broadcom wi-fi exploits), which won't happen for devices that are out of support.

[0] https://cve.lineageos.org/kernels

Re:Remotely Compromising Android and iOS via a bug in Broadc... by nosajm on Wednesday July 26, 2017 @10:13PM (#14862149)
My five-year-old Samsung S3 for Verizon stopped receiving updates less than 2 years after its release. The bootloader is locked tight, so I am unable to install any custom ROMs such as Lineage OS.
Re:Remotely Compromising Android and iOS via a bug in Broadc... by contingencies on Wednesday July 26, 2017 @09:25PM (#14861921)
My phone screen was eaten alive by fungi last week, so I had a look at the field to pick a new device. Discovered Lineage OS, super keen. Unfortunately, its device support is crap.
Re:Remotely Compromising Android and iOS via a bug in Broadc... by ams6110 on Thursday July 27, 2017 @12:46AM (#14862780)
Guess I'll have to look at upgrading my diehard old Moto G. It's still on Android 5.1.1.

Meanwhile I guess disabling WiFi is a mitigation?

Re:Remotely Compromising Android and iOS via a bug in Broadc... by kbenson on Sunday July 30, 2017 @04:44PM (#14887714)
> Meanwhile I guess disabling WiFi is a mitigation?

That's a good question. If it's disabled in firmware and not actually powered down, it might still be susceptible.

Re:Remotely Compromising Android and iOS via a bug in Broadc... by zerocrates on Wednesday July 26, 2017 @09:11PM (#14861849)
My TV came with no on-screen menus but a tablet you use to interact with most features and settings: it's on the June... 2016 patch set. It was over half of year out of date before I took it out of the box.