[investigation] what other intrinsics should be remapped about near-membrane HOT 3 OPEN

Some browses are using internal slots for Errors (Firefox, we are looking at you), which might interfere with the remapping mechanism because some accessors might through when an error is passed from outer realm into sandbox (think of Promise.catch maybe). We should validate this.

from near-membrane.

It looks like things like Date.prototype.getTime() Map.prototype.get can't be remapped safely unless you remap the methods and re-dispatch based on where they are object of remote realm or object of current realm.

https://github.com/mmis1000/secure-ecmascript-sandbox/blob/4afbe936ec5e309c6d56ac9758e2a4139d07d8a2/src/browserRealm.ts#L855-L863

but that has another problem.
unless you also remap the methods in outer realm.
Date/Map and other object that relies on internal slot created in inner realm won't work in outer realm.

Some class I found that has method/getter relies on internal slot

https://github.com/mmis1000/secure-ecmascript-sandbox/blob/4afbe936ec5e309c6d56ac9758e2a4139d07d8a2/src/browserRealm.ts#L87-L120

These won't work unless you remap the methods.

In turns, it means these need to be whitelisted as this object when calling methods of these class. But that sounds dangerous to me though.

from near-membrane.

I have identified another small list of intrinsics that are present in node 12.x when creating a new VM:

  [ 'BigUint64Array', 'BigInt64Array', 'BigInt', 'WebAssembly' ]

from near-membrane.