News for hackers. Stuff that matters.
Re:Don't use JSON web tokens for sessions by merb on Monday June 13, 2016 @05:51PM (#11898015)
if you are vulnerable to XSS your HttpOnly cookie won't help you.
Re:Don't use JSON web tokens for sessions by SCHiM on Monday June 13, 2016 @06:02PM (#11898092)
You are wrong. It does. It keeps your user's session from being trivially stolen. In practise this makes successfully executing attacks harder. It's not a _nice_ thing to have, it's essential.

An example of this is an application that asks you to confirm <action> after a POST or w/e. If your XSS vector is not in the new page, then you can't execute <action> as an attacker automatically.

Many, many, applications (not only on the web) implement such a scheme.

A stolen session is MUCH more valuable to an attacker than only a raw XSS.

Re:Don't use JSON web tokens for sessions by tptacek on Monday June 13, 2016 @07:11PM (#11898525)
It does not. It is the difference between an exploit that yields a root password and one that yields a shell at uid=0.

HttpOnly is almost totally cosmetic.

Re:Don't use JSON web tokens for sessions by SCHiM on Tuesday June 14, 2016 @07:56AM (#11901389)
It's not the same, an XSS is not comparable to a shell for the exact reason I outlined above. And a session is not a password.

I'm probably coming over as too offensive, but you really really don't seem to know what you are even talking about. You are wrong wrong wrong.

Re:Don't use JSON web tokens for sessions by kkl on Tuesday June 14, 2016 @11:46AM (#11902767)
If you don't believe `tptacek maybe you will believe James Kettle:

http://blog.portswigger.net/2016/05/web-storage-lesser-evil-...

Re:Don't use JSON web tokens for sessions by tptacek on Tuesday June 14, 2016 @09:59AM (#11902041)
I'm pretty sure? I do know what I'm talking about here. Sorry. HttpOnly is a joke.