Patched MS Bluetooth Flaw Exposes Even Disconnected PCs
An anonymous reader writes "Among the 22 security holes Microsoft issued updates to fix yesterday is a critical kernel-level Bluetooth flaw that could let nearby attackers break into vulnerable systems even when the targeted computer is not connected to a network. An attacker could use the bug to gain access to any unpatched, Bluetooth-enabled Windows Vista or Win7 computer within 100 meters (or much further with specialized tools), all before the target system even gets an alert that another computer is requesting a Bluetooth connection."
Teh evil hax0rs r in ma b0x!
XP is safe
Sounds ridiculous for a system software used in military installations, cash machines, banks, and pretty much everywhere. And that's not even the 'government way' of reaching into private information, which is at least encrypted. It's pretty much 'no way of knowing who and if' data was seeped out.
I cannot imagine more definitive example of Unsecure.
Still nothing will change. MS will issue a patch and the thing will go as nothing happened. Cash will continue to flow and that's the only thing that will be monitored.
On a related note: http://www.swfme.com/view/1046212
"even when the targeted computer is not connected to a network."
"target would merely need to have Bluetooth turned on."
Meh, not as scary as I thought. You shouldn't be running around with bluetooth on anyway. Also, if you're using a 'hidden' connection there's no real way for an attacker to find you is there?
So basically computers at risk are those who always leave bluetooth on and shown to everyone. Which unless you're trying to connect to a new device should be NEVER.
From MS SB
The vulnerability could allow remote code execution if an attacker sent a series of specially crafted Bluetooth packets to an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
Almost remote full admin access. Seriously how much worse can it get, guess your still safe from internet attacks but still.
Anyone found a page on the exploit, you can do the entire list of immature things to other peoples computers to all your friends with Bluetooth with this one.
A worm that infects computers within a 100 meters of itself? That's a novel way of bypassing firewalls. The exploit would need to be paired with a traditional network vulnerability for the worm to spread far from the point of origin though.
You mean all those super secure non-networked military computers that even have bluetooth adapters?
95 is saferer
If it's Bluetooth-enabled, it's not really disconnected, is it?
This is like saying "if your computer's attached a LAN, other people on the LAN can attack it, even if there's no Internet connection". Duh - you're still connected to the LAN, which is where the attacker is. Same here: you've got Bluetooth enabled, so an attacker can use Bluetooth to attack you.
When Microsoft salts LAN Manager passwords then I'll get excited. Who cares if you can raise privileges by some nefarious means when you can crack the admin password by brute force:
http://www.ethicalhacker.net/content/view/94/24/
http://en.wikipedia.org/wiki/LM_hash
Having installed the three patches (KB2507938, KB25342531, and KB2555917) on a fully patched Windows 7 Dell Laptop, I immediately started experiencing BSODs. System Restore to the pre-patch state failed, but I was able to uninstall the patches through the add / remove utility. After the uninstall the BSODs immediately stopped. I have not had time to individually install each one to determine the culprit. But please take this as a heads-up.
What really they meant was, every single laptop ever made with bluetooth.
Or with your GPU, eg
http://mytechencounters.wordpress.com/2011/04/03/gpu-password-cracking-crack-a-windows-password-using-a-graphic-card/
losing yet another method of gaining access to a target PC...
Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
Trolling fail. "[..] versions prior to Windows NT", and not used by default since before Vista.
This would only be interesting if it were an Apple flaw. Then we could jump on in droves and condemn those insecure Apple users and their poorly designed and built hardware and software.
Might be fun walking through a computer shop (or just some offices...) with this on... And coming near to one of those giant display walls at a trade fair would be still better...
From advisory:
"A remote code execution vulnerability exists in the Windows Bluetooth 2.1 Stack due to the way an object in memory is accessed when it has not been correctly initialized or has been deleted. An attacker could exploit the vulnerability by constructing a series of specially crafted Bluetooth packets and sending them to the target machine. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights."
No fun driving yet another Windows drops it's panties vulnerability into the ground. Instead let's make fun of Bluetooth and relate your worst Bluetooth experience.
Me first, I got the cell phone and the Garmin navigator talking via bluetooth. Love answering calls on the Garmin while driving. Hands free, sounds good, love it.
Ok, I do not love parking the truck, going into the convenience store, getting a call and the navigator picks it up when I open the flip phone. I cant hear them, they cant hear me cause their audio is routed to the fricking truck which is locked up out in the parking lot while I am picking out a 6 pack of beer.
This "even disconnected" ./ title really got me wondering if there is a WakeOnBluetooth technology.
Like every other OS. Granted, an interesting new attack vector/approach.
Vote monkeys into Congress. They are cheaper and more trustworthy.
I noticed newer OSes of Linux/Debian, Windows, Mac OS X, etc. have Bluetooth features. I wished I could yank them out since I don't have any Bluetooth devices or plan to. Why keep the bloats and possible security holes?
Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
I fail to see how a PC with an active wireless network standard enabled, can be considered "disconnected".
Bluetooth has long been a target of undesirable types, its just that a PC is a richer target than most peoples phones full of garbage apps.
I remember installing windows without a firewall, where I'd have to sneakernet technet patches to the machine before enabling internet access. Looks like I need a faraday cage now.
I guess that rule of thumb no longer rings true. Get it? Rings...
Having to work for a living is the root of all evil.
Bluetooth has always been a known attack vector. I remember one that affected symbian phones for example. I used to get the odd file transfer request on my phone from other people who were infected. I think this might have been it.. http://www.f-secure.com/v-descs/cabir.shtml
@ the root - Disable BlueTooth oriented functionality, temporarily only if needed, until patch is issued
http://www.google.com/search?hl=en&source=hp&q=Disable+bluetooth&btnG=Google+Search
Yes... really simple, & that's how good things are made/done imo (the "KISS" principle, doing more with less etc.)
What I liked seeing while reading thru this, is it's good to see that others here are sensible enough to do that themselves now, without guidance too!
Personally, I've been doing things like that & from as far back as 1997 & putting them out "onto the wire' for "public consumption" too, ala my 1st speed & security guide for Windows -> http://web.archive.org/web/20020205091023/www.ntcompatible.com/article1.shtml
Just as a "pay-it-forward" type of thing, & a "contribution back to society"...
Hey - It was done for myself by others in this art & science of computing before me, & they too, "stood on the shoulders of giants" before they also...
Yes - imo, it's just how it works (I once saw Madonna say how she "turned her life around", & she DID, by being of service to others... so, I took from her & others' example. Why not? It's the right thing to do, & there IS a "joy in giving" as well!)
That 1st guide of mine on security/speedup for Windows NT-based OS LATER evolved into this in 2008 "layered security" model (much better, & far, Far, FAR more comprehensive & adjusted for today's more modern Windows NT-based OS too):
http://www.bing.com/search?q=%22HOW+TO+SECURE+Windows+2000%2FXP%22&go=&form=QBRE
Yes - @ first I did guides like that circa 1997-2000 so folks got the "most" out of their rigs as I was... & yes, initially @ least?
Just to save CPU cycles, RAM ops, & other forms of I/O wasted on services + features in Operating Systems that run by default, that I actually don't use...
(Dumb to do, like leaving your lights on in your home, during the daylight hours really!)
HOWEVER - Later, when I figured the "malware explosion" was about to "hit" (circa 2004 it really did, & my HOSTS file population programs can prove that much for me)?
I realized that there's security benefits (around 2000) to doing the same as well ("Double-Bonus", yea!, right?)
* In any event - ONE THING MICROSOFT'S BEEN really, Really, REALLY GOOD ABOUT, is when things like this occur? They issue an "emergency-out-of-band" fix...
(So - Expect it shortly is my guess here, IF it's really needed/necessary, that is...)
APK
P.S.=> Well - time to go fix my lawnmower & snowblower (yes, bit early, but a "stitch-in-time, saves 9" on the latter)
... apk