Skip to content

Conversation

@darrachequesne
Copy link
Member

…erating parsing error

Note: sanitization should occur upfront

Closes #61, fixes (partially) socketio/socket.io#2459

@darrachequesne darrachequesne merged commit f5d966b into socketio:master Sep 26, 2016
@Nibbler999
Copy link

I think it would be better to stick with utf8.js and catch the exception. We need to do that anyway because wtf-8 will still throw on other kinds on invalid input.

Also, https://simonsapin.github.io/wtf-8/#intended-audience specifically says:

WTF-8 must not be used to represent text in a file format or for transmission over the Internet.

@calzoneman
Copy link

Any news on when this version will be targeted by socket.io? Currently, socket.io 1.4.8 brings in engine.io-parser 1.2.4, which does not have this fix. I'm having to manually patch my deployments right now because this bug can crash the server if not sanitized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants