Linux Has a USB Driver Security Problem (bleepingcomputer.com)
Catalin Cimpanu, reporting for BleepingComputer: USB drivers included in the Linux kernel are rife with security flaws that in some cases can be exploited to run untrusted code and take over users' computers. The vast majority of these vulnerabilities came to light on Monday, when Google security expert Andrey Konovalov informed the Linux community of 14 vulnerabilities he found in the Linux kernel USB subsystem. "All of them can be triggered with a crafted malicious USB device in case an attacker has physical access to the machine," Konovalov said. The 14 flaws are actually part of a larger list of 79 flaws Konovalov found in Linux kernel USB drivers during the past months. Not all of these 79 vulnerabilities have been reported, let alone patched. Most are simple DoS (Denial of Service) bugs that freeze or restart the OS, but some allow attackers to elevate privileges and execute malicious code.
you're already pwned
I think i found the problem. Kernel Space drivers are always prone to these kinds of problems. This is not new.
The depth of the problem is newish, but only because someone peeked in and saw flaws.
Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
Attacker with physical access owns local machine. Film at 11.
Linux drivers can mitigate that but they will never stop the problems in the USB spec.
Vulnerabilities present and reported in the kernel-based DRIVER FOR A TOY since *2003* and still not fucking fixed.
The kernel should do nothing more than act as a basic bit router.
Most other OSes get this right. Why can't Linus in his infinite wisdom do the same?
Oh, right, his inability to be fucking wrong.
Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
See subject: Khyber, when you're RIGHT? You're right but with problems too see below. Monolithic design = dumb vs. modified hybrid micro/monolithic kernel designs (w/ drivers for hardware vs. internal to OS core type) yes, like Windows NT based OS are (a hybridized kernel design between BOTH models).
* You do "monolithic"? Well - THIS is EXACTLY what can "go wrong" (or rather need a fix) but it gets more complicated when it's embedded in an ENTIRE KERNEL vs. a driver file instead (smaller by FAR & usually pretty small code vs. usermode apps).
HOWEVER:
You're describing & leaning toward PURE MICROKERNEL design though (has problems too, messagepassing overheads between RPL0/Ring 0 kernelmode & OTHER layers (usually RPL3/Ring 3 in current OS design typically)).
Seriously though? Go easy man - you'll POP getting so "tight" about this - @ least they KNOW about it now & can fix it (look @ the 'bright side').
APK
P.S.=> Anyhow, see subject = For once, I am with you & this article proves a lot of it for you... apk
Severs in locked data centers - safe
PCs in locked offices / homes - safe
Laptops - safe if you shut it down and have bios password to enable boot, probably safe with encrypted root fs, provided machine is shutdown to begin with.
Laptop in yours own hands - safe
Now all those consumer devices that the manufacture won't let you have access to, ROOTED!
This is a win.
Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
They never shoulf haz kiked me off of vger.kernel.org. I could help get them a code and help them more I bet while I'm trying to help.
Nick Krause
The same applies to all devices that have loadable firmware. Just you do not hear as much about malicious SATA drives, malicious MODEMS, and malicious monitors.
However, they can all do exactly the same thing.
He'd like MACH purer 'microkernel' design but it has the downside YOU & I noted (messagepassing) https://linux.slashdot.org/comments.pl?sid=11332813&cid=55515443/
* Too bad too - in theory, microkernel design IS more secure & easier to maintain I'd say (separated driver files AND rings of privelege) but has messagepass overheads between priv rings.
APK
P.S.=> I'd say it's slower than 20% though... apk
I'm assuming these things happen because the USB device drivers load microcode from the USB device? If so why can't these things be sandboxed-- no reason to give them file access or network access or even much memory. If it's a matter of top line speed then let the user decide-- sandbox by default and let the user have a switched labeled "open your mouth and close your eyes-- give me a tiny bit more speede in return for butt neckid security."
Some drink at the fountain of knowledge. Others just gargle.
The quality of website is inversely proportional to the number of third party scripts, adware, and trackers which it hosts. BleepingComputer is one of the WORST offenders. It is a junk website loaded up with an extra heaping helping of gratuitous scripts. The only thing surprising about BleepingComputer is that they don't use more html "blink" tags.
is that they were discovered precisely because someone could look at the sourcecode. The same vulnerabilities in Windows or Macos would've taken far longer to fix. In addition, bugs like these are often fixed very fast on Linux, but on Windows and Macos it can take months and months, as has been proven before, mainly because somewhere in the chain there is a court order typically from the NSA, in order to make sure there is a "way in" on certain computer systems.
Bugs occur on all systems, that's the reality, and if anything this should inspire confidence in Linux and how it's developed.
Really? That seems like a lot.
It has always been well known best practice to minimize threat surface by minimizing code on a system, including the most obvious of not having code you don't have an intended use for being present. And there have always been a spectrum of devices and use cases where various tradeoff levels between security and convenience were taken.
That large companies raking in the bucks might have made dubious due diligence in their following of these practices, as well as smaller less/non-profitable software developers overselling the relative security of their products... Yeah, we've know there has been a lot of that for many many years now.
Post Snowden this counts as little more that typical slashdot hype headlining. (If my didn't bother to read half the summary analysis isn't otherwise flawed). Also, if there is perhaps a less chromatically offensive, but widely enough understood to 'whitelists' i'm all ears. But it boils down to the general best practice of knowing what you intend, and spending as much time as you can justify encoding that that, and only that, is what goes on in the system. hashtag overall system code minimization. keep it (as) simple (as reasonably possible) stupid.
So, i guess it affects android too..
Oh, i see your phone is low on battery, here - have a charger
If they can tell that the part of he disk is encrypted, it's bad encryption (implementation).
The whole point of encryption is, that you can't tell what it is. That includes "nothing" and "encrypted data" as choices.
Yeah, that means everything needed to locate, decrypt, open and mount the encrypted partition, should reside, in a password-protected form, on this USB stick that "happened" to already get destroyed.
If they lock you up for that, they will lock you up in any case, unrelated to anything you did.
It's the law to inform the people you may have infected them with an STD, no? Otherwise, what kind of asshole are you?
Authors of Qubes OS have long stated that monolithic kernel crappiness means that Linux, Windows kernels cannot be used effectively for security. The solution is to isolate the risk (large attack surface) they pose using relatively secure type-1 hypervisors. USB and NIC/wifi/bluetooth controllers are compartmentalized in their own virtual machines.
Linux is Safe. There is no USB exploit. Now all you people stop talking right now!
My penis is stuck in the toaster and it's burning!
It's not just USB drivers.
I think you're confusing cryptography and steganography..
So when you plug in a flash drive, you are giving control of your entire computer to it. Every time. Like when your kids give you a USB with something to print from their virus riddled school.
At least Windows is no longer supposed to automatically execute code it finds on the drive (or CD, if that is what the USB is emulating). But it is *long* over due that I should be able to plug in a USB drive and still be safe. May need special ports. Or a rule that Keyboards are only detected on startup. Etc.
I've worked in secure environments and as someone that has obtained security certifications I see all kinds of problems with USB beyond improperly coded drivers. One common practice not that long ago was to disable any USB ports to stop people from plugging in things they weren't supposed to. This was only possible while PS/2 ports for keyboards and mice were still commonplace. (There was also that short period where some Apple computers had both ADB and USB ports.)
I like USB-C. It's quite the improvement over what we've had before. I am a bit concerned on how this affects the security of our devices in the future. Controlling things like someone offering a "charger" for a laptop or cell phone to try to sneak into a device can be managed in many ways. Dedicated ports for video, keyboard, mouse, and even Ethernet had inherent security in that they did only so much which prevented certain security issues. Will all these ports go away and be replaced with USB-C?
Again, I really like USB-C as it adds convenience and capability that nothing else offered before. It also adds security issues that a simple list of "dos and don'ts" cannot cover for many less technically knowledgeable people to follow. Securing computers from many kinds of attacks is going to be an increasingly difficult problem unless we get off this mentality of one port to rule them all.
Maybe we'll see some means to better secure USB. Maybe we'll see computer systems that will allow one to disable anything that is not a HID or power device from being recognized on USB in the firmware. Maybe OS developers will provide better granularity on what USB ports are allowed to do.
Maybe we'll get PS/2 ports back again. Probably not. I do think something has to give. If we can't have the inherent security of feature limited ports then we will need some security through better management of the ports that replace them.
I am armed because I am free. I am free because I am armed.
Who can ? Affirmative action strikes home maty! You are an HIV+ nibberizing gaffot in California ... blome the job and you can futtbuck any progressive stain. That's Wein...stain ... eh hoser ?
So whereâ(TM)s your patch?
Nope, he isn't.
CLI paste? paste.pr0.tips!
It is rather simple...
If a computer has a disk...
It will either be formatted by the vendor (usually results in known data).
If it is used - then it will contain data.
If it is encrypted... then it will still contain data, just randomized by the encryption.
thus you can determine fairly reliably that it is or is not encrypted...
And who has a disk connected to a computer that doesn't use it?
Where I worked previously the computers had a piece of software that acted as a USB filter: only devices with specific USB IDs would be permitted. So the keyboard would work, the mouse would work, and a specific make and model of USB memory sticks issued by the company would work. Nothing else would even register if you plugged it in.
That seems like quite a bit of the solution. Of course a sufficiently well motivated attacker could probably find out what kind of USB devices are permitted on your system and produce some custom malhardware that had the right USB ID to get through the filter. But that's expensive. It's not your average hacker kiddy. If your threat model includes threat actors capable of mounting such a complex and bespoke attack against you then your options are significantly different to the average Joe, who doesn't need to be faster than the bear, only faster than the slowest person in the group.
Yes, he is. Encrypted data should be indistinguishable from random data.
An unused drive is not typically filled with random bits. Finding a drive full of random bits is a good indication that it's encrypted.
See subject & as you EAT YOUR WORDS brockmire/QUAGmire https://slashdot.org/comments.pl?sid=10557875&cid=54347839/
* :)
Tell us - how did EATING YOUR WORDS taste?
(A bit like YOUR FOOT IN YOUR MOUTH ramming your empty trolilng words back down your chicken-neck throat washed down by the 'bitter taste of your SELF-defeat vs. myself, as always, lol...)
APK
P.S.=> Lastly -get this straight: You don't give me orders BOY - get over yourself psychopath - you don't "run me", get it? Good (but I run your ass off easily, every SINGLE time, lmao - easily)... apk
See subject: It's moot when YOUR HOST DELETES MY POSTS as he has again here https://tech.slashdot.org/comments.pl?sid=11332773&cid=55516015/, here https://tech.slashdot.org/comments.pl?sid=11332773&threshold=-1&commentsort=0&mode=thread&pid=55515797/ & here today https://tech.slashdot.org/comments.pl?sid=11332773&cid=55515877/
* NOT A FIRST... want more?
APK
P.S.=> Incredible - want to KNOW when you are winning debates? When not only BOGUS unjustifiable downmods are used (I blow by those via unlimited posting ability) but WHEN YOUR POSTS ARE DELETED & yet not defeated by VALID technical fact (Fuck truth: It's relative, facts, are not)... apk
Was the USB stuff not written by that nice geek gurl that got so upset that she left after she had to to listen to Mr L's abbrassive rants? Ducks-n-go-hides.
With a dongle : http://hexus.net/tech/news/per...
With some Linux 'firewalls' : USBGuard, https://github.com/dkopecek/us... , USBauth, https://github.com/kochstefan/...
Nice paper on LWV, that's still paying this week but will become free after 8 days as usual : https://lwn.net/Articles/73830...
HTH,
Hervé
BTW : anyone in region 06 in France wishing to share shipping costs for the dongle?
Herve S.
One solution to that problem is to completely (first to last sector) overwrite the disk with random data, then create a partition table and a legitimate filesystem on top of that, add some legitimate files, map the sectors that constitute free space of that filesystem to a logical contiguous block device, create crypto container on top of that, create filesystem on top of that, mount, enjoy.
CLI paste? paste.pr0.tips!
A stack of hard disks sitting next to my computer and containing a total of around 8 TB actual pseudorandom data beg to differ. Also every hard drive that was bought used and sold by someone with a little knowledge.
CLI paste? paste.pr0.tips!