Optional Windows Update Aims To Halt Wireless Mouse Hijacking
Reader itwbennett writes: An optional Windows patch released Tuesday protects against an attack, dubbed MouseJack that affects wireless mice and keyboards from many manufacturers, including Microsoft and allows attackers to spoof a wireless mouse from up to 100 meters away and send rogue keystrokes instead of clicks to a computer. According to a Microsoft security advisory, the devices affected by this attack are: Sculpt Ergonomic mouse, Sculpt Mobile Mouse, Wireless Mobile Mouse 3000 v2.0, Wireless Mobile Mouse 3500, Wireless Mobile Mouse 4000, Wireless Mouse 1000, Wireless Mouse 2000, Wireless Mouse 5000 and Arc Touch Mouse. But Marc Newlin, one of the researchers who developed the attack said on Twitter that the patch doesn't go far enough and 'injection still works against MS Sculpt Ergonomic Mouse and non-MS mice.'
Now can we get an update that prevents anything from ever stealing keyboard focus and stops popups from preventing me from moving their parent window around?
If it is possible to negotiate rogue key/mouse input (which presumably requires proper communication between the rogue keyboard/mouse and the target device), then would it not also be possible to capture the data from the real keyboard/mouse? And in that case, it would seem quite possible, then, to steal keystrokes/mouse movements -- say during someone's login.
From what I can gather without any real detail in the rather useless article Microsoft are looking for timing discrepancies to try to detect this attack. Normally packets come in at regular intervals, so if one comes outside the regularly expected window it is considered malicious. There must be some clever filtering because the clock on the keyboard/mouse will drift in relation to the computer etc.
This could be overcome by simply replicating the timing of the keyboard/mouse. They don't transmit constantly to save battery power, only when a key is pressed or the mouse is moved.
Anyone know if Bluetooth keyboards are vulnerable?
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
...In the other news, the update might be riddled with the umpteenth GWX :-)
I had my wireless mouse hijacked last night. Battery committed suicide.
Do I have this right?
The update that downloads and installs Windows 10 over your existing Windows system is turned on by default.
The update that protects your system from a vulnerability is optional.
Microsoft never was a very "customer centric" company.
I always look at MS updates as 'no telling what else MS is installing at the same time'. I stopped the so called security updates long ago. I also managed to stop MS from continuously trying to update my W7 to 10 and don't want to open myself to that intrusion again. When I can't get W7 anymore, it is off to Linux for me.
Encryption breaks this attack. Evidently many of the wireless peripheral manufacturers use the same chipset (RTFA). The chipset will support encryption but the device manufacturers have to write their own drivers to implement the encryption. Most have chosen not to.
Bluetooth peripherals encrypt by default but unless you are using a tablet it is damn near impossible to buy a Bluetooth keyboard and mouse. Logitech made the excellent MX 5500 Revolution set (I have two) but discontinued them a few years ago. Someone on Amazon is asking $650 for unopened examples. Not sure he has sold any at that price.
There's chatter on the Ubuntu boards that a recent Winblows update is removing grub on dual boot systems.
I have Windows 10 Pro on my laptop using a Microsoft Wireless Mouse 1000. Updates were installed Tuesday afternoon. I have updates set to install updates for other Microsoft product. I presume that their Wireless mouse 1000 is an "other" product. Device manager shows that my mouse driver is dated 2006. When checking for new drivers I get a message "the best driver for your device is already installed". Sure it is at ten years old. Assholes. Windows 10 is fucked up.
If you're going to leave Windows on the box, use ITS boot menu to dual boot.
I have a test laptop with 4 boot targets for the Windows boot process: Recovery, Windows 7, OpenBSD, and GRUB (which can, of course, also boot Windows). OpenBSD put its boot loader at the start of its partition, as did GRUB. With Cygwin installed on Windows (or booting from a "Live" of some sort, copy those boot blocks to files in Windows' C:\, and reference them in the Boot Configuration Data. OpenBSD's FAQ has a very nice tutorial section 4.15. GRUB is used to boot between several flavors of Linux for testing (yes, I could use VMs, but OpenBSD, at least, likes bare metal best, and it's no harder to copy back a specific partition than VM image).
http://www.openbsd.org/faq/faq4.html#Multibooting
It's sad, but nowadays we have to ask that of every patch Microsoft releases. Especially the optional ones.