Disabling ASLR for binaries executed in the autograder disallowed

[dkohlbre]

Hi,
I teach a security course where some of the assignments involve writing exploits for simple targets.
To make this easier on the students, we disable ASLR and enable exec stacks.
On our servers this is relatively easily done with calls to personality (e.g. personality(ADDR_NO_RANDOMIZE |READ_IMPLIES_EXEC))

When I've tried to build an autograder for this assignment I can't make those calls from a binary running in the Docker container.
(Nor can you do things like modify the relevant /proc/ bits, its mounted RO)
As far as I'm aware, this is due to the seccomp policy the container is run under. I don't believe you can modify that policy from the container image, only from the way the container is started.

Does anyone have a solution for disabling ASLR/execstack for specific binaries inside the autograder?

Thanks.

[cfm]

It looks like it would be possible to add support for these personality() calls in gVisor.¹² There's been discussion about whether gVisor itself requires some modification to run under Docker's default seccomp profile, but there's a more-recent production use-case documented in https://github.com/freedomofpress/dangerzone/blob/main/docs/developer/gvisor.md.

Footnotes

1. https://github.com/google/gvisor/issues/153 ↩

2. https://github.com/google/gvisor/issues/10756 ↩