3 ms·
> In today's arms race of exploits, you need to operate and prepare your interactions with computers with a defined threat scenario. This is never-ending. Ther
by woodruffw 4y ago
> In today's arms race of exploits, you need to operate and prepare your interactions with computers with a defined threat scenario. This is never-ending.
There are very, very few threat models in which a 219 bytes/sec kernel memory disclosure is not catastrophic. Even in an ideal world where disclosing kernel memory wouldn't help an attacker bypass KASLR, it's catastrophic for any key material that happens to be in kernel memory.
- paulmd 4y agoKASLR is already broken on AMD systems. #1 is unpatched (AMD says "it doesn't directly leak memory", only the page table mappings, ie breaks KASLR) and #2 the PREFETCH+TLB-Evict combo is still unpatched unless you use non-default hardened configs (only mitigated by enabling KPTI which AMD recommends be disabled by default). #2 also allows a Meltdown-style attack which exfils data directly but hey, also breaks KASLR too. https://mlq.me/download/takeaway.pdf https://mlq.me/download/takeaway.pdf https://mlq.me/download/amdprefetch.pdf https://mlq.me/download/amdprefetch.pdf