News for hackers. Stuff that matters.
Re:AwSnap – This link crashes Chrome by ahoge on Monday April 06, 2015 @12:16AM (#9326484)
The port number is supposed to be a 16-bit number though. So, anything above 65535 is malformed.

http://en.wikipedia.org/wiki/Port_%28computer_networking%29

Re:AwSnap – This link crashes Chrome by Smerity on Monday April 06, 2015 @03:01AM (#9326962)
Agreed that it's malformed. My point was more that I'm curious how many other libraries fail badly when confronted with an unexpectedly large port. It's the edge cases / "no-one would ever be silly enough to do that" that quite frequently lead to security issues =]
Re:AwSnap – This link crashes Chrome by jlblatt on Monday April 06, 2015 @03:10AM (#9326980)
Yes, that's why I feel like this is more significant than a simple crash at first glance- no one would purposefully craft a 256+ unchecked character URL, unless they are being malicious, in which case they absolutely will craft a 256+ unchecked character URL.
Re:AwSnap – This link crashes Chrome by userbinator on Monday April 06, 2015 @04:53AM (#9327196)
URLs can definitely get rather long if they contain lots of query data, and the de-facto limit seems to be around 2KB[1]. It's still not acceptable for such URLs to crash the browser though.

[1] http://stackoverflow.com/questions/417142/what-is-the-maximu...