Live data from Hacker News

"Hacking" Skrill/Moneybookers, Bitbucket, Github, Heroku etc

homakov.blogspot.ca

11–20 of 37 posts

Re: "Hacking" Skrill/Moneybookers, Bitbucket, Github, Heroku etc

#11
post #10
post #8

Earlier quoted context omitted.

Can you explain? My understanding was that cookies will not be sent in these attacks (I validated this only testing some approaches, namely doubleclick and other ad embeds). Without cookies, how would the CSRF attack access my account? Or have I missed something obvious?

Disabling third party cookies disables cookies in certain contexts, like when loading images and frames from another domain, but there are other ways to perform a CSRF attack. A link or form that doesn't target a frame would still work.

Got it that makes sense. It seems like a link would be a real problem to solve and keep the web usable. The form approach seems easy enough to solve with a dialog. The others that can be solved via tighter cookie restrictions probably should be.. Too many permission dialogs and you end up annoying the user, or worse, train them to accept without reading.

Re: "Hacking" Skrill/Moneybookers, Bitbucket, Github, Heroku etc

#12
Well I already posted it, nobody is interested. Okay :( I guess you should change the title - this on is too shouting.

Sorry all that I took your time for considering the problem.

I see you are not interested to do/solve anything and my arguments worth nothing.

Re: "Hacking" Skrill/Moneybookers, Bitbucket, Github, Heroku etc

#13
post #12

Well I already posted it, nobody is interested. Okay :( I guess you should change the title - this on is too shouting. Sorry all that I took your time for considering the problem. I see you are not interested to do/solve anything and my arguments worth nothing.

This is currently the #2 post on Hacker News; I think people are interested.

Re: "Hacking" Skrill/Moneybookers, Bitbucket, Github, Heroku etc

#17
post #14

I don't understand how this is so widespread - If you're using a major web framework, and most of these sites probably are right? isn't CSRF protection built in? are people just turning it off?

Even in the major frameworks, on-by-default CSRF protection is relatively new. On some popular J2EE platforms, forms still aren't protected by default.

We'll get there. This is a much more straightforward problem to solve than XSS, which is the real bitch.

Re: "Hacking" Skrill/Moneybookers, Bitbucket, Github, Heroku etc

#20
Serious kudos for Homakov.

And he has a point. While I dislike the whole "lean startup" thing a lot of people promote and adore it. And along Learn, Measure, Adapt, Innovate and other big words, I don't see a Secure your Damn App section.

When I write my controllers I can't focus completely on my product - I also have to think if this mass assignment is vulnerable.

Post reply on HN