-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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.
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
vm.runInContext is memory unsafe and can be used to dump core #8537
Comments
vm.runInContext
is memory unsafe and can be used to dump core
This is a known issue and affects most C++ API functions accepting non-primitive values. For more information: |
I don't think this fits under that category. (We're the ones that found #7902 FWIW) This is already using |
It's a variation on the same theme. CopyProperties() uses |
@bnoordhuis thanks for hint. Proposed fix in #8649. Sorry if it is way off base. |
This commit prevents thrown JavaScript exceptions from crashing the process in node_contextify's CopyProperties() function. Fixes: nodejs#8537 PR-URL: nodejs#8649 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Franziska Hinkelmann <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ilkka Myller <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
This commit prevents thrown JavaScript exceptions from crashing the process in node_contextify's CopyProperties() function. Fixes: #8537 PR-URL: #8649 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Franziska Hinkelmann <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ilkka Myller <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
vm.runInContext
is memory unsafe and can be used to dump core.This doesn't seem like a serious security vulnerability (hence my reporting here), but can certainly be used to cause DOS and it might be nice to have a stdlib that is memory safe.
Related to: #8539, #8538, #7902
The text was updated successfully, but these errors were encountered: