Android Security

Recommendations

Info

Top 3 Risks Top 3 risks - #3: File Formats • File Formats: Codec, HTML/CSS, JS – Vector: Remote (and also Local) – Impact: Privilege Escalation – usually media/drm/system – Reason: overly complex formats, interpreters • Particularly, CSS/JS parsing, media files – Countermeasures: • Standard Code Injection Countermeasures • SELinux (C) 2016 Jonathan Levin & Technologeeks.com - Share freely, but please cite source!
Top 3 Risks Top 3 risks - #3: File Formats • Case Study: – (Another) StageFright Bug (CVE-2015-3864) – http://googleprojectzero.blogspot.com/2015/09/stagefrightened.html – https://github.com/NorthBit/Metaphor – https://www.exploit-db.com/exploits/38226/ (C) 2016 Jonathan Levin & Technologeeks.com - Share freely, but please cite source!
Page 1 and 2: Android Security: Same-ol’, Same-
Page 3 and 4: Android Internals::about “Android
Page 5 and 6: Mobile Security Trusted app may be
Page 7 and 8: Local Attacks (rogue app, malware)
Page 9 and 10: Android Security A little history (
Page 11 and 12: Android Security Android Applicatio
Page 13 and 14: Android Security Android Code Bases
Page 15 and 16: Android Security Updates (or lack t
Page 17 and 18: Code Injection Prelude: Vectors for
Page 19: Counter- CounterMeasures for Code I
Page 23 and 24: Top 3 Risks Top 3 risks - #2: Binde
Page 25 and 26: Top 3 Risks Top 3 risks - #1: Linux
Page 27 and 28: Untrustworthy TrustZone Android & T
Page 29 and 30: Untrustworthy TrustZone Android Vul
Page 31 and 32: So, overall.. • Sad Truth: Androi

Android Security

Create successful ePaper yourself

Delete template?

Save as template?