Android 'root' phones via dirtyc0w exploit

Security and privacy

exploit automation

SHOW HN2016

143points
67comments
#239of 2,264 in 2016
Top 11%of 2016 by points

How HN took it

CuriousMostly questions and neutral comments

2 positive, 26 neutral or asking, 0 mixed, 9 critical, out of 37 comments about the project. Thread score -0.17.

Privacy: 0 for, 4 againstIdea: 1 for, 2 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Useful, timely script

    From 1 comment

Objections

  • Downloading and running unverified scripts as root is risky

    From 2 comments
    • I wonder how many people carelessly run a script that downloads, builds, and executed something with root access. If that zip gets compromised (i.e. The source means harm) there…
      bastijn on HN
    • That is really true. Any solution you propose? I mean, it is all open source, but if the author of the PoC repository were to put malicious code into the file, how would we know…
      Arinerron on HN
  • Script was broken at first and the exploit repo was not the author's

    From 2 comments
    • The first goo.gl link is dead for me... Care to give the real link instead of a shortened URL? Edit as noted elsewhere, should be https://github.com/timwr/CVE-2016-5195
      ce4 on HN
    • Okay, sorry guys. I know it's broken right now. The problem is that wget and unzip commands aren't being used properly. I can't fix it on my phone, because the editor isn't…
      Arinerron on HN

Requests

  • Give direct links instead of shortened URLs

    From 1 comment
    • The first goo.gl link is dead for me... Care to give the real link instead of a shortened URL? Edit as noted elsewhere, should be https://github.com/timwr/CVE-2016-5195
      ce4 on HN

Questions

  • Does root survive a kernel patch, and can SELinux block it

    From 3 comments
    • Sure, but as soon as it's patched out, you're back to no root.
      scrollaway on HN
    • Maybe I'm missing something here, but what stops you from putting a setuid "su" binary and keeping the root access, even if the kernel is upgraded?
      omribahumi on HN
    • You're root running in a limited selinux context.
      therein on HN

Alternatives named

  • Original CVE-2016-5195 exploit repo by timwr

    From 2 comments
    • This is just automating running the exploit from here: https://github.com/timwr/CVE-2016-5195
      edsouza on HN
    • The first goo.gl link is dead for me... Care to give the real link instead of a shortened URL? Edit as noted elsewhere, should be https://github.com/timwr/CVE-2016-5195
      ce4 on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/12802785)