3 ms·
Getting all the pieces to line up in order to take advantage of this behavior – serving an ad to a site that asks for a logon, the user using an on screen (or v
by chris_wot 14y ago
Getting all the pieces to line up in order to take advantage of this behavior – serving an ad to a site that asks for a logon, the user using an on screen (or virtual) keyboard, knowing how that onscreen keyboard works – is hard to imagine.
ORLY? The imagination of a Microsoft engineer quite clearly is no equal to the imagination of a creative exploiter. After all, nobody could imagine the Morris Worm, or Word Macro viruses, or even SQL Slammer.
Attacks come through exploitable vectors. Lining up those exploitable vectors may seem tricky, but that hasn't stopped this from happening. And frankly, this particular attack vector seems to be one of the more exploitable ones.
- mattmanser 14y agoI don't agree at all. It's an x, y position, what possible use is it? Two integers. MS are right about this, this is just spider.io being alarmist for free publicity.
- ambrop7 14y agoSo you're saying if you were given a mouse movement trace on top of a virtual keyboard, you couldn't possibly deduce what was typed? Someone should just make a program that does that, and this will all be settled. Maybe even make it guess what kind of virtual keyboard was used.
- kevingadd 14y agoA better question is what degree of danger this information actually poses. It is possible to reverse a password hash created by bcrypt regardless of what settings you used. The question is HOW LONG would it take, and whether the cost makes the value of any potential exploit less than zero. If the value is less than zero, the risk is effectively minimal - at least for now. Panic and tarring and feathering of Microsoft's security team is only justified if the risk is severe.
- jbri 14y agoA security issue is a security issue, regardless of how severe it is. If MS had come out and said "We're working on fixing it, but we don't think it's a critical vulnerability" - that would be understandable. What needs to be called out is if they come and say "This isn't an issue at all". If some website was leaking password hashes, would "well the hashes are so strong that this isn't really an issue" be an acceptable response?
- DuskStar 14y agoYeah, but you still wouldn't want sites making their bcrypt hashes publicly available...
- wglb 14y agoWell, the underlying software uses just this information (x, y position) to translate the movements of the mouse to individua l key events. Since the OS does it, it is not in the same ballpark as stuffing a dictionary down bcrypt's throat. While the risk may not be severe, and not of the scale of tarring let alone feathering, it is a risk that must be addressed. As the article says, We take these risks very seriously.
- flixic 14y agoIf password is sufficiently long, x and y coordinates are all what is needed to deduce keyboard coordinates, button size and then, password.
- Aardwolf 14y agoJust use Dvorak and they'll have no idea what you typed :)
- ch0wn 14y agoThey seem to have never seen terminal PCs. I know a couple of places in my city where you have IE-based kiosk terminals with touch-on-screen keyboards that emulate a cursor. It should be even much easier to map mouse movement to actual inputs as the emulated cursor "jumps" from key to key during input.
- nmcfarl 14y agoMy recollection is that those PCs don't allow background windows. And this attack works in all browsers for the foreground window.
- dbaupp 14y agoI don't think it does work in all other browsers. At least in Firefox on Linux, the mousemoves are only triggered when the mouse is directly over the page itself, not even when over the tab-bar etc, nor when over the Gnome 3 on-screen keyboard (which overlaps the page).
- wglb 14y agoThat is admittedly a weak part of their response, but to their credit in the previous sentence they say We take these risks very seriously.
- Aardwolf 14y agoSaying is not doing.
- marcosdumay 14y agoThe entire buleting stands for: "We take these risks very seriously. We analised it, and concluded that we shouldn't take this risk seriously."
- chris_wot 14y agoThey did what with it?