-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
add no-sandbox flag #3863
add no-sandbox flag #3863
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
failing test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Implementation: lgtm
Note: this change will prevent nuclei from connecting to private ipv4/ipv6 ranges, making it unusable within VPC, CI/CD, and internal pipelines. I recommend evaluating carefully before proceeding (a possible solution could be to implement different level of sandboxing with still internal ranges enabled by default).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since sandbox component involves, disabling both can cause issues for default behavior, we can expose file and network options with separate CLI options to have better control and nonbreaking changes.
-lfa, -allow-local-file-access allows file (payload) access anywhere on the system
-lna, -restrict-local-network-access blocks connections to the local / private network
Suppressed by #3927 |
Proposed changes
The PR removes the sandbox flag and makes the sandbox mode default. In addition, it adds a no-sandbox flag to allow users to turn off the default sandbox mode if they choose to do so. Closes #3784.
Checklist