3 ms·
So, I was curious what the Google vulnerabilities are, and it looks like quite a few of them at notes as "On Samsung S3 through S5 devices..." which seems to in
by kbenson 10y ago
So, I was curious what the Google vulnerabilities are, and it looks like quite a few of them at notes as "On Samsung S3 through S5 devices..." which seems to indicate it's not an Android problem, but a Samsung extensions to Android problem.
It's interesting, because depending on why you're looking, you might want those combined and you might want those separated. If you are interested in an Android phone, you are interested in the vulnerabilities from Google's software that apply, as well as the vulnerabilities of the phone provider if them are extending Android. If you are buying a Nexus or Pixel device, you don't care about Samsung or HTC vulnerabilities. If you just want to know about problems in Google's suite of web applications, you don't necessarily care about Android at all.
Similarly, for Apple you might want to know the track record of their phones, or you might want to know about their OS's. For windows, you might want to know about base OS vulnerabilities, or phone vulnerabilities, or Office and other application vulnerabilities.
For large companies, attributing all vulnerabilities to the company may not be the most useful way to do this. Also, if you want to know how responsible a company is, it might be more useful to provide a vulnerabilities to employed software engineers per company ratio. If company X has 10 vulnerabilities and 10 programmers, and company Y has 100 vulnerabilities but 10,000 programmers, company Y may look worse on a pure vulnerability level, but conceivably they could be doing a really good job at writing secure software, but they are just putting out a lot more software.
- cryptarch 10y agoI don't think that's quite right or at least incomplete. I think that when developing software that runs on many, many platforms different platforms will have different interactions with the software which can sometimes result in bugs. Sometimes the fault will be with the platforms, e.g. when the bug results from POSIX noncompliance, and sometimes the platform will interact with the program in a valid but unusual way, that isn't covered by the program and thus results in a bug.
- kbenson 10y agoI agree with this, but this isn't what I was referring to. I was referring to things like CVE-2016-7989 which says: On Samsung Galaxy S4 through S7 devices, a malformed OTA WAP PUSH SMS containing an OMACP message sent remotely triggers an unhandled ArrayIndexOutOfBoundsException in Samsung's implementation of the WifiServiceImpl class within wifi-service.jar. This causes the Android runtime to continually crash, rendering the device unusable until a factory reset is performed, a subset of SVE-2016-6542. Note where is says "Samsung's implementation", and specifically mentions that it affects Samsung devices. That's not an android interaction with the hardware platform, that's a completely different company altering the software to market a customized device, and those alterations included vulnerabilities. It's almost like Adobe's vulnerabilities in Acrobat reader being attributed to Microsoft because it runs on Windows.