News for hackers. Stuff that matters.
Re:LastPass autofill exploit by kmiroslav on Wednesday July 27, 2016 @08:10AM (#12172109)
I don't quite follow. The author says that by entering the URL "http://avlidienbrunn.se/@twitter.com/@hehe.php", the extension is fooled into autofilling as if the browser was on twitter.com.

What's the difference with simply going to "http://twitter.com"?

This looks more like a bug than a vulnerability, what am I missing?

Re:LastPass autofill exploit by rietta on Wednesday July 27, 2016 @08:12AM (#12172121)
A bug that tricks the secure password management tool into revealing your Twitter password to a website that is not Twitter! That's a pretty major security vulnerability due to a bug in URL parsing.
Re:LastPass autofill exploit by kmiroslav on Wednesday July 27, 2016 @08:22AM (#12172171)
But the information is not sent to the server, it's simply pasted in the text field.
Re:LastPass autofill exploit by tronje on Wednesday July 27, 2016 @08:34AM (#12172217)
Yes, but some JavaScript can detect that the text field has been filled, and then send the information back to the attacker's server. An (innocent) example of this is when you type something into Google's search field, and you already see suggestions, even though you haven't clicked anywhere or hit Enter yet.
Re:LastPass autofill exploit by K0nserv on Wednesday July 27, 2016 @08:12AM (#12172120)
An attacker could fool the extension to autofill a form on a domain they control with credentials from another domain and send the credentials to their server.