Consider escaping lone surrogates

[mathiasbynens]

Lone surrogates are not valid in UTF-16 or UTF-8, and can be (and have been) used to break such parsers. To protect against this, just escape them.

• Explanation: https://speakerdeck.com/mathiasbynens/hacking-with-unicode-in-2016?slide=106 (there’s a video recording too)
• Related ECMAScript proposal: https:/tc39/proposal-well-formed-stringify

FWIW, I worked on https:/mathiasbynens/jsesc which shares devalue’s security goals (although it does not compete with devalue, as it doesn’t aim to support cycles).

[Rich-Harris]

Thanks! I opened #17, but I have to confess I don't really know what I'm doing. Does it look like a reasonable solution? Essentially it replaces JSON.stringify with a stringifyString function that behaves equivalently (in theory) except for the handling of lone surrogates.

[mathiasbynens]

Note that with https:/tc39/proposal-well-formed-stringify, JSON.stringify should behave equivalently (modulo casing for hex digits in escape sequences). V8 v7.2.10 / Chrome 72 implements this.

[mathiasbynens]

Closing now that #17 is merged. Cheers, Rich!

[mathiasbynens]

Would jsesc make sense in this list? https:/Rich-Harris/devalue#see-also

[Rich-Harris]

yeah! added it