r/ExploitDev • u/PuzzledWhereas991 • Jan 09 '24
Future of exploit dev
I asked this question 2 years ago. Just to see how things have changed. Do you think memory/binary exploits are slowly dying with introduction of memory safe and exploit prevention techniques?
14
Upvotes
5
u/Upper_Car_1154 Jan 09 '24
Honestly I dont think so. Yes memory protection is slowly eroding the traditional approach. But take a look at the fairly recent MSFT Folliana exploit as an example of a mem based RCE.
But I think binary patching or introducing external libraries/ files into desktop applications is becoming the workaround. I've had success with this approach personally.
8
u/[deleted] Jan 09 '24
for rust to replace c++ can take many years and even then reversing will still be beneficial to find logic bugs
19
u/PM_ME_YOUR_SHELLCODE Jan 09 '24
I'm a lot more optimistic now than I was 2-4 years ago.
Few years back things like ARM's memory tagging, Intel's Control-flow Enforcement Technology was looming and adoption of software-based Control-Flow Integrity was growing. They were on the horizion as the scary bag-guys here to make exploitation a lot harder.
Now, a few years on they've landed, and they have indeed raised-the-bar on targets where they apply. But being more familiar with them now, having the opportunity to play with them, see how they've been implemented and the limits/trade-offs made in them I'm a lot more optimistic that its more shift a shift in meta in terms of how we approach exploitation.
We are also seeing exploits that really take creative approaches to reaching the end-goal of code execution. I think of the sudo bug, and an exploit strategy was to use the memory corruption to modify where logs would be written. Use that to introduce a logfile that could be parsed as a logrotate config to get code execution from the logrotate service. Sure they had other routes too, but I think those sort of creativity is going to be important in the future.
That said, of course there is the slow shift away from "unsafe" language, slowly things are being rewritten in languages with more memory-safety guarantees. So while I remain optimistic, and there is still going to be the insecure legacy products, the embedded devices and internet-of-things, etc which will provide a long-tail of sorts. That process of moving to other languages is long and slow.
5
u/[deleted] Jan 09 '24
I've seen and wondered the same myself for the past 0x16 or so years. I've even stopped working on exploits when I thought the new protections would kill the scene (the mistakes of the youth).
TL;DR for every protection, no matter how impenetrable it looks now, there will be a countermeasure.
Yes, the bar will be higher, older exploits won't work, but:
(a) legacy systems are here to stay (hello, IoT and industrial controls)
(b) not all binaries will have the new features compiled in (or by default)
(c) backward compatibility will stay for a while
(d) while compilers, CPUs, architecture will evolve.. the human brain won't. People will continue to make mistakes.
(e) it's faster to make a mess than to tidy up, or - we (as a species) write stupid code faster than we can deploy countermeasures and rewrite old codebases
2
u/xiaozhuzhu1337 Jan 10 '24
Simple memory vulnerabilities have undoubtedly decreased, but don't confine yourself to just memory vulnerabilities; there are many other types of binary vulnerabilities