Replies: 1 comment 3 replies
-
Echo CSRF is so basic/naive that it should be pretty much considered as a measure for copy/pasting links from untrusted source or a measure against double posting. It does not store token even in session - just cookies - it compares CSRF you posted from form and compares it to token in cookie. I think worrying about BREACH is least of your problem if your browser starts to guess COOKIE through compressed traffic - at this point you might as well read the cookie (is |
Beta Was this translation helpful? Give feedback.
-
I was reading golang/go#73626, and it made me wonder about echo's csrf implementation.
Unless I am reading the code incorrectly, Echo doesn't seem to "mask" the token placed into the context, and if the user is using a
TokenLookup
ofquery:
orform:
, it seems like it would be vulnerable to a BREACH attack?gorilla/csrf
does do masking.I also wonder if any of the other recommendations in that linked Go issue would be a good idea to implement in echo's csrf protections.
Beta Was this translation helpful? Give feedback.
All reactions