You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently a lot of Deno runtime code is vulnerable to prototype tampering. Just like Node, we should copy a frozen version of all JS primordials as the first step before loading deno_core, and use that for all internal JS implementation.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
Currently a lot of Deno runtime code is vulnerable to prototype tampering. Just like Node, we should copy a frozen version of all JS primordials as the first step before loading
deno_core
, and use that for all internal JS implementation.We have some failing WPT that are caused by this.
This will be a rather large undertaking, but maybe we can fork off some of the Node primordial init code to speed this up. Ref https://github.com/nodejs/node/blob/2eeb4e1d944b4ebebcf80261d9250bc86eadc89a/lib/internal/per_context/primordials.js
We will need to highly vigilant about performance issues that arise from using primordials due to unexpected V8 deopts.
The text was updated successfully, but these errors were encountered: