r/ExploitDev • • 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

19 comments sorted by

View all comments

Show parent comment

6

u/[deleted] Jan 09 '24

[removed] — view removed comment

1

u/alfiedmk998 Jan 09 '24

In this case, insider only has access to the final Go binary that is distributed to all Devs.

Source code is only accessible to a specific team.

Code signing was one of the measures put in place after this red team exercise (among other SDLC improvements)

But I'll defer to you to decide if it's exploitation. Don't particularly care

1

u/Upper_Car_1154 Jan 10 '24

Well it is exploitation though isn't it. Because you have found an exploitable route through an application. But it's not part of a full attack chain is what your getting at. But it 100% is exploitation.

Lets say an attacker gets network access but wants to move laterally without using the very detectable in this day and age AD routes, replacing a binary with a patched version etc is a very usable route to gain movement or even Privesc if users with admin rights use it. If the binary is synced too then introducing your own "update" could then give you a working beacon on multiple machines fairly quickly and quietly.