[WIP] mmap randomization #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Draft

topimiettinen wants to merge 1 commit into master from mmap-randomization

Owner

topimiettinen commented Oct 11, 2021

Signed-off-by: Topi Miettinen [email protected]


          [WIP] mmap randomization

fad9319

Signed-off-by: Topi Miettinen <[email protected]>

topimiettinen marked this pull request as draft

October 11, 2021 19:16

Owner Author

topimiettinen commented Oct 11, 2021

Once this works, similar approach can be taken with mremap(): in case MREMAP_MAYMOVE is specified, force move and randomize the address.

I've proposed the same for the kernel (1/2, 2/2).

Owner Author

topimiettinen commented Oct 12, 2021

Maybe SECCOMP_RET_USER_NOTIF could be used to force the change even if other libraries don't cooperate. It's not perfect since it requires NoNewPrivileges, so it can't be used when setuid programs should work. But it would make sense as an optional feature.

sonarqubecloud bot commented Aug 30, 2023

SonarCloud Quality Gate failed.

1 Bug
0 Vulnerabilities
0 Security Hotspots
6 Code Smells

No Coverage information
0.0% Duplication

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet