Integrate Snow with LavaMoat scuttling protection

[weizman]

This PR follows up on LavaMoat/LavaMoat#462 which allows exporting the scuttling security feature to an outside scuttler (as an experimental feature ⚠️ ).

This in fact allows us in MetaMask to perform scuttling not only to the top main realm, but to all potential child realms using Snow.

In other words, if an attacker wants to access alert but can't because the alert property is scuttled, the attacker could have opened an iframe (aka new realm) and extract the alert function from the global object of that iframe.

With this PR, Snow will automatically apply the scuttling mechanizm to all new potential child realms, including the iframe described in the example, thus leaving the attacker unable to get a hold of an alert function instance.

The alert example is merely a demonstration of course, but scuttling all windows recursively brings an important security benefit to MetaMask (will be elaborated in the future).

[socket-security]

New and updated dependency changes detected. Learn more about Socket for GitHub ↗︎

Packages		Version	New capabilities	Transitives1	Size	Publisher
lavamoat	⬆️	6.4.0...7.1.0	None	+0/-1	38.9 kB

Footnotes

1. https://docs.socket.dev ↩

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue	Package	Version	Note	Source
Unpublished package	lavamoat	7.1.0	Version: 7/1/2000, 12:00:00 AM	package.json

Next steps

What are unpublished packages?

Package version was not found on the registry. It may exist on a different registry and need to be configured to pull from that registry.

Packages can be removed from the registry by manually un-publishing, a security issue removal, or may simply never have been published to the registry. Reliance on these packages will cause problem when they are not found.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore lavamoat@7.1.0

[codecov]

Codecov Report

Merging #17969 (4c909fb) into develop (16dad66) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop   #17969      +/-   ##
===========================================
- Coverage    70.80%   70.79%   -0.01%     
===========================================
  Files          988      988              
  Lines        38366    38366              
  Branches     10042    10042              
===========================================
- Hits         27162    27160       -2     
- Misses       11204    11206       +2     

see 2 files with indirect coverage changes

need to update scuttleName config

[digiwand]

^ nvm, LGTM! 🙌🏼

[Gudahtt]

LGTM!