News for hackers. Stuff that matters.
Re:Steam hit by major security breach by ghuntley on Monday July 27, 2015 @12:36AM (#9953366)

    * Accepting the email address to send token to from web user, 
      validating the address, and then using the user input directly
      as the email address to send the token to; as in: systems that
      will send token to [email protected];[email protected].
Ouch, that's really devious and extremely clever.
Re:Steam hit by major security breach by noir_lord on Monday July 27, 2015 @02:33AM (#9953686)
I think that might work on one of the apps I maintain.

Sigh adds to wunderlist

Re:Steam hit by major security breach by __david__ on Monday July 27, 2015 @03:55AM (#9953931)
I'm missing something here... How does "[email protected];[email protected]" validate as "[email protected]"? Is this a regexp vs strcmp() issue or is there something more subtle at play?
Re:Steam hit by major security breach by pfg on Monday July 27, 2015 @04:05AM (#9953962)
One scenario I can imagine is a regex which doesn't properly handle multi-line inputs (quite common issue in ruby[1]). Together with a mail header injection vulnerability, this input could be dangerous:

  [email protected]\nCc:[email protected]
[1]: http://guides.rubyonrails.org/security.html#regular-expressi...
Re:Steam hit by major security breach by mikeash on Monday July 27, 2015 @11:51AM (#9955873)
Total speculation, but maybe they're trying to be clever and accept things like "John Doe <[email protected]>" as being equivalent to "[email protected]" and end up using a full e-mail parsing library for the matching which is more capable than they realize?
Re:Steam hit by major security breach by AUmrysh on Monday July 27, 2015 @03:37PM (#9957491)
It may send it to multiple addresses. I know in outlook and in .NET libraries, the semicolon is the delimiter for multiple email addresses.
Re:Steam hit by major security breach by mpeg on Monday July 27, 2015 @04:17AM (#9953998)
Might have been validated in step1, but the email goes out to the email in a hidden field in step2, etc.