21 ms·
> That said, authors should follow responsible disclosure, give the game company some time to respond before releasing. Stack-smashing attacks have been around
by dvt 7y ago
> That said, authors should follow responsible disclosure, give the game company some time to respond before releasing.
Stack-smashing attacks have been around since at least 1988[1]. This cheat has less to do with the game itself and more to do with the computing architecture (i.e. stack-based). ROP is an active area of research and "code hardening" is a way to mitigate such an attack[2], but (from what I understand) usually comes with performance penalties.
[1] https://lwn.net/Articles/732201/ https://lwn.net/Articles/732201/
[2] https://cs.brown.edu/~vpk/papers/ccr.sp18.pdf https://cs.brown.edu/~vpk/papers/ccr.sp18.pdf
- jakear 7y agoI don't see your point. Do you think the authors shouldn't give responsible disclosure because the underlying mechanism has been around for a while? The company would obviously fix the area where false data is allowed to be injected, not systematically harden their entire codebase against any possible ROP-based attack.
- kuroguro 7y agoThere are going to be hundreds or thousands more, possibly outside of their code. They are easy to introduce in your code, fairly easy to find and hard to fix. It's more of an idea or PoC on how to write cheats than a specific exploit. On another note it's not an exploit in the classic sense - if you own your game you're legally allowed to do what you want with it in most countries AFAIK. I'm not convinced responsible disclosure even applies here.