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
That is, the value is correctly restored, but the taint object is left as null. This changes the semantics of the typeof operator, which is problematic if you are sending properties of the client to yourself via post message.
The text was updated successfully, but these errors were encountered:
While debugging stuff related to the primitive tainting, I noticed something that breaks some applications in a subtle way.
If I send a tainted string via post message, it gets cloned, transferred, and deserialized as expected. The same sadly is not true for numbers.
I would expect this to print something like:
but instead it is as follows:
That is, the value is correctly restored, but the taint object is left as null. This changes the semantics of the
typeof
operator, which is problematic if you are sending properties of the client to yourself via post message.The text was updated successfully, but these errors were encountered: