News for hackers. Stuff that matters.
Re:Rails Commit: Whitelist all attribute assignment by default by oconnore on Sunday March 04, 2012 @08:37PM (#3664978)
How would you be losing sleep now? Assuming you were Github, as of now you would have (1) identified the problem, (2) fixed the issue, (3) handled the public relations with a press release that includes a future disclosure policy. You probably blew some cash on overtime pay this weekend, but how do you count 5-6 figures?

Any company that is paranoid enough to cut their Github contract following a benign intrusion that was resolved in under 24 hours is not a company that would have uploaded code in the first place. This is not the only security vulnerability on Github.

I think you are being excessively dramatic.

Re:Rails Commit: Whitelist all attribute assignment by default by maratd on Sunday March 04, 2012 @09:11PM (#3665084)
> (2) fixed the issue

They were notified of the issue 3 days ago. Today, he simply found another instance of the very same problem in a different place. The vulnerability is throughout their entire code-base.

They are not even close to resolving this.

Re:Rails Commit: Whitelist all attribute assignment by default by patio11 on Sunday March 04, 2012 @08:54PM (#3665033)
See below. 99% of the total cost isn't accrued yet.