This repository has been archived by the owner on Dec 19, 2023. It is now read-only.
Mitigation for arbitrary code execution / sandbox breakout #1
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.
📊 Metadata *
Bounty URL: https://www.huntr.dev/bounties/1-npm-safer-eval
⚙️ Description *
Mitigating potential sandbox breakout by checking user supplied input for statements that might be trying to manipulate system processes.
💻 Technical Description *
After a couple attempts at specifically addressing the
RangeError
mentioned in the disclosure, I ended up going with a simpler solution of checking the user supplied template literal for statements that might be trying to access system processes that they should not be accessing. This solution involvesrunInContext()
logging a warning to the console and returningundefined
if this situation is detected, otherwise it returnsvm.runInContext
the same as before.🐛 Proof of Concept (PoC) *
Unit tests based on existing proofs of concept:
https://gist.github.com/JLLeitschuh/609bb2efaff22ed84fe182cf574c023a
commenthol#10
commenthol#11
🔥 Proof of Fix (PoF) *