4 ms·
> The security implications of RWX memory are just so bad Such as? Any practical examples here? Code executions is code execution. RWX just lets you execute f
by kllrnohj 8y ago
> The security implications of RWX memory are just so bad
Such as? Any practical examples here?
Code executions is code execution. RWX just lets you execute faster code, it doesn't give you any privileges or permissions you didn't otherwise already have.
- gok 8y agohttps://www.jaybosamiya.com/blog/2019/01/02/krautflare/ https://www.jaybosamiya.com/blog/2019/01/02/krautflare/
- kllrnohj 8y agoWhich didn't need RWX by using ROP chains instead...? The security vulnerability there was that the process had the ability to invoke shell at all, not how they got to invoking shell. In-process sandboxing isn't a thing anymore, spectre proved that. In that context what risk does RWX actually pose?