Added new option to restrict unsafe memory access#11
Open
chris-t-k wants to merge 1 commit intokhaleesicodes:mainfrom
Open
Added new option to restrict unsafe memory access#11chris-t-k wants to merge 1 commit intokhaleesicodes:mainfrom
chris-t-k wants to merge 1 commit intokhaleesicodes:mainfrom
Conversation
Contributor
Author
|
The included test was my first approach to defeat the sandbox. It is not a matilda bug but a java exploit/backdoor to get full reflective access without the need to open a module. Credits for this approach go to Project Lombok. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
sun.misc.Unsafe can be used to bypass the sandbox. Matilda should control access to that class.
Alternative: Make sure Unsafe is disabled using -Dsun.misc.unsafe.memory.access=deny