4 ms·
> And it's reasonably sandboxed in recent Android versions using selinux. Is it safe to assume that this attack vector is not a concern with Android 5.1? (or l
by Florin_Andrei 11y ago
> And it's reasonably sandboxed in recent Android versions using selinux.
Is it safe to assume that this attack vector is not a concern with Android 5.1? (or later)
- ajross 11y agoCertainly not, because the plausible kernel bugs in those open driver descriptors (I'm serious: vendor media drivers are not pretty things) would obviously not be subject to selinux controls. But at least there is some sandboxing in place; the security architecture was designed to admit the possibility of a breach of the mediaserver.
- fluidcruft 11y agoAccording to the reddit discussion, 5.1.1 is demonstrated to be vulnerable (so it affects everything 2.2 and later).
- ajross 11y agoLink to that reddit thread? AFAICT, all current claims are for a crash exploit into libstagefright, not a breakout of the mediaserver to (for example) persistently write a payload/rootkit.