I live in fear of being told my factory delivered Dell rackable servers have been EFI infected since inception on my network. It's silly to pretend a BSD OS is going to be immune of the consequences of an EFI which is compromised at birth. Sooner or later there will be a value chain in compromising my OS, through the EFI. I wish we had better out of band EFI validity checks, based on what the manufacturer thinks shou…
You can use the Dell Trusted Agent to to do just that: https://www.dell.com/support/kbdoc/en-us/000126098/what-is-d...
CosmicStrand: The discovery of a sophisticated UEFI firmware rootkit
51–60 of 125 posts
Re: CosmicStrand: The discovery of a sophisticated UEFI firmware rootkit
#52That's why things like the Pluton processor and TPMs are useful. (A rain of downvotes falls on me) Seriously, even good old BIOS is susceptible to rootkits, there has been tons of them. So no crying over UEFI please. We need a fully signed and auditable chain of trust for booting OSes. Of course all this crap needs to be open source but it needs to be locked down to prevent not trusted binaries as much as possible. A…
Re: CosmicStrand: The discovery of a sophisticated UEFI firmware rootkit
#53Re: CosmicStrand: The discovery of a sophisticated UEFI firmware rootkit
#54That's why things like the Pluton processor and TPMs are useful. (A rain of downvotes falls on me) Seriously, even good old BIOS is susceptible to rootkits, there has been tons of them. So no crying over UEFI please. We need a fully signed and auditable chain of trust for booting OSes. Of course all this crap needs to be open source but it needs to be locked down to prevent not trusted binaries as much as possible. A…
Re: CosmicStrand: The discovery of a sophisticated UEFI firmware rootkit
#55Earlier quoted context omitted.
Most modern exploits on this level are extremely difficult to get onto users machines - without any conspiracy at play, you would have to essentially get users to run untrusted code, and for general use case there are a whole bunch of blockades against this. For private entities seeking financial gain, its completely pointless to burn a zero day like this for the return that you would get.
Really ? On some of my computers the UEFI partition is a FAT32 partition writable by anyone by default.
Re: CosmicStrand: The discovery of a sophisticated UEFI firmware rootkit
#56Hah, this reminds of a security researcher a few years ago that was reporting malware that he couldn't research without infecting his other machines. I'm fuzzy on the details, but everyone wrote him off as a paranoid delusional and the incident was quickly swept under the rug. Makes me wonder if he found some sophisticated state sponsored stuff and got smeared to hush it up. I mean realistically, we'd be naive to not…
Re: CosmicStrand: The discovery of a sophisticated UEFI firmware rootkit
#57I remember being called a reactionary naysayer like, 8 years ago, because i told that this would happen.
Re: CosmicStrand: The discovery of a sophisticated UEFI firmware rootkit
#58I remember being called a reactionary naysayer like, 8 years ago, because i told that this would happen.
A lot of people don't like negativity so strongly that they'd rather be screwed over than have to consider the possibility that something bad is happening.
Re: CosmicStrand: The discovery of a sophisticated UEFI firmware rootkit
#59Such sophisticated attacks always amaze me, and I've always wondered how people go about developing them in the first place.
someone who worked on the UEFI implementation writes it
now if you were handed only the binaries, and left to objdump them etc, how long? evidently there’s symbol names since the article uses those. so hopefully no more than an extra order of magnitude: a couple weeks, maybe a full month if my manager’s asking for a deadline and i want to be conservative?
also, think about where/how they hooked: it sounds like they hooked at the equivalent of an interface boundary, where it’s easiest to inject a new implementation — but then they have to check the return address to know where in the larger scope of the process they’re currently at: if you had access to the codebase and build tools why wouldn’t you patch your exploit into the code more directly and just rebuild it? why abuse the return address like that?
i don’t mean to say it’s not impressive, but it’s not magic. there are lots of competent engineers out there capable of reverse engineering a UEFI implementation.
Re: CosmicStrand: The discovery of a sophisticated UEFI firmware rootkit
#60Earlier quoted context omitted.
A lot of people don't like negativity so strongly that they'd rather be screwed over than have to consider the possibility that something bad is happening.
A lot of people don't like idealism so strongly that they'd rather stick with old hardware over the newest hyped-to-death shit.