ASLR is not quite dead yet. Those new techniques still need some time to read thru all memories. Fork+reexec+ASLR will throw a big wrench in those PoC.
1
2
until someone has spectered/rowhammered their way into sshd its hard to argue against your viewpoint. I predict this will come sooner than later and new mitigations will need to be developed. 35%-65% perf hit isnt going to cut it for all.
1
1
buying enough time to implement proper mitigation is what it's all about.
You see lots of PoC out there that only work when you disable some mitigations like aslr or canaris... there is a big difference between a practical PoC and an actual exploit, fortunately.
1
what you and me see here is just the tip of the iceberg. Real exploits are being developed using these new techniques as we speak.
1
I expect it's still going to take enough time for practical exploits to emerge that most things are going to get patched first.
I'm more worried about rushed fixes that will open other avenues to exploit.
Of course, there's still the possibility of a "perfect storm" situation
1
1
agreed, rushed buggy patch would be the worst. From my understanding there wont be any proper fix however, only workarounds. Maybe openbsd comes up with something smart and innovative? :)
1
I didn't invent ASLR (I invented ASCII armoring for shared library mappings, which might be a precursor but it's not ASLR). I think ASLR will survive last year's & yesterday's attacks, even if it's now understood to be quite limited (KASLR was understood that way from the start).
2
4
you implemented very early mmap "randomization", which was the first (?) time the notion of ASLR was introduced. Higher entropy ASLR surely has been developed since then... but nonetheless you inspired what became ASLR. @paxteam did a lot of work with PIE later on
2
I think you misrecall. While I played with changing mmap addresses (ASCII armoring), I did not introduce any randomness in there. Others did.
1
i coined ASLR back in 2001 when i actually created it. you should know better since you were also around (sous bock? :). i also added ET_EXEC randomization on top of ET_DYN (PIE these days) because you said it wasn't possible... good memories!
Jan 11, 2018 · 12:39 AM UTC
2
7
7



