4 ms·
Wow. Had a very similar CSRF problem once. Customer complained they were getting page expired errors constantly. But only one customer and only with Safari,
by tedunangst 15y ago
Wow. Had a very similar CSRF problem once. Customer complained they were getting page expired errors constantly. But only one customer and only with Safari, not Firefox.
Turned out they were using an RSS reader on OS X that shared the system cookie jar with Safari. Every ten minutes it would log in with a password and get a new session cookie. Safari would then use the new session cookie which didn't match the CSRF form value.
- Figs 15y agoHow did you resolve the problem?
- simcop2387 15y agoI'd probably check to see if they had a valid login already and not update the cookie. Not sure if that opens up other holes though.
- tedunangst 15y agoWe made the CSRF depend only on the user ID, which doesn't change, instead of the session ID.