3 ms·
I've briefly examined the mentioned commit in response to the sandbox escape [1], and am way out of my comfort zone here, but I basically can't understand how
by tannhaeuser 3y ago
I've briefly examined the mentioned commit in response to the sandbox escape [1], and am way out of my comfort zone here, but I basically can't understand how setting seccomp policies can be effective in the presence of an exploitable buffer overflow (cf. max size check and mention of ASLR failure/compromise).
[1]: https://gitlab.gnome.org/GNOME/tracker-miners/-/commit/f0c880a0ec0e650dbdc037c59e58e07442f82fef https://gitlab.gnome.org/GNOME/tracker-miners/-/commit/f0c88...
- josephcsible 3y agoBuffer overflows can result in remote code execution, but it'll be within the same process, and there's no way to turn seccomp back off.