Critical EFI Code in Millions of Macs Isn't Getting Apple's Updates (wired.com)
Andy Greenberg, writing for Wired:At today's Ekoparty security conference, security firm Duo plans to present research on how it delved into the guts of tens of thousands of computers to measure the real-world state of Apple's so-called extensible firmware interface, or EFI. This is the firmware that runs before your PC's operating system boots and has the potential to corrupt practically everything else that happens on your machine. Duo found that even Macs with perfectly updated operating systems often have much older EFI code, due to either Apple's neglecting to push out EFI updates to those machines or failing to warn users when their firmware update hits a technical glitch and silently fails. For certain models of Apple laptops and desktop computers, close to a third or half of machines have EFI versions that haven't kept pace with their operating system system updates. And for many models, Apple hasn't released new firmware updates at all, leaving a subset of Apple machines vulnerable to known years-old EFI attacks that could gain deep and persistent control of a victim's machine.
That was a pretty weak attempt at emulating the Luddites App spam post...
Just give us control over our own damn equipment! Let us form our own communities that will service these machines as necessary.
Why is everything shrouded in a goddamn fucking mystery? WHY?!
Even older version of EFI should run newer OS systems just fine. And really, any vuln in the EFI is going to be of the sort that requires physical hands on device to exploit. If that's the situation you're in, you have much larger problems my friend. Apple probably understands this and hasn't bothered to throw a lot of resources at what really is a non-issue.
Apple's solution is probably "buy a new Mac". Tim Cook said himself that Apple products are not for the rich so buying another $1000+ computer every year or two shouldn't be a problem for anyone. Next up: Tim Cook doesn't understand the meaning of "rich" compared to the rest of the population.
#DeleteFacebook
If Apple doesn't want to throw resources at it, then fine.
But why can't I throw resources at it? Give me the source code of the firmware, and allow me to install an upgraded version in my own time.
but one thing I see surprisingly frequently on the Surface Pro is EFI firmware updates.
That can be seen as a good thing and a bad thing. One would hope these are feature updates and not such a long list of critical vulnerabilities but .... Microsoft.
Your comment is not funny, interesting, or helpful; your comment is entirely a waste of cyberspace. The next time you feel compelled to write such a banal comment, don't.
But don't let that stop a good Apple ass-whoopin'... carry on.
Beware of the Leopard.
I guess you would say this is another example of Apple simply dropping support in a way most users won't notice. I would say many PC makers also stop doing bios updates as well after a few years. Not excusing either of this but it does appear to be something not exclusive to just Mac's.
Locked hardware, leak of support, 1 year only hardware warranty, higher prices. Thatâ(TM)s Apple.
Duo is a bunch of hacks. Interviewed there and was penalized when getting the correct C++ answer because the interviewer was offended I found another valid way to solve his problem. Because my solution was simpler than his, he was so offended they never called me back.
They have a hatred of the guys who work on GRSec kernels and after mentioning in the interview I used those in the past, they were dead set against me. Get that, a security company upset someone knows GRSec and C++ openssh programming.
They have one smart dude who does this type of work and the rest just piggyback to try to make the company look good. I'm half tempted in my spare time to write an openssh SMS verification plugin and open source it to put them out of business. Some day when I get some spare time.
Has this negatively impacted users or present a vector for hackers that has been exploited?
It's Apple's way to call you out as a peasant and strongly encourage you to buy a new machine. They've been doing this since the 1980s. Consider them the masters the rest wish they were.
Thank you for being a friend
Traveled down the road and back again
Your heart is true, you're a pal and a cosmonaut.
And if you threw a party
Invited everyone you knew
You would see the biggest gift would be from me
And the card attached would say, thank you for being a friend.
It's time to upgrade again and throw out your glued in batteries and ssds for a new system
http://saveie6.com/
I still use a haswel i7 at home and needed to replace a damaged board. All the popular MSI, Gigabyte, and Asus boards with 97 stopped being updated with new EFI.
I googled for Windows 10 compability and use the latest 2015 UEFI flashes.
Do Macs need them updated or tied to specific releases of MacOSX?
http://saveie6.com/
Not sure this is solely an apple issue. Does anybody have any knowledge of EFI update issues across the industry they might share?
your mom
your dad
So...
How do I check if I am using the latest EFI firmware for my mac?
I can see what version I"m using, but the only Apple support page showing version numbers that I could find stopped at 2014 models.
Apple's users need to declare their independence from dependence on Apple and switch to free software OSes running on hardware they own. The same is true for independence from any proprietor.
You will never get the control over your own damn equipment you seek so long as you do business with proprietors (Apple, Google, Microsoft, etc.). Like I've said so many times before on /., the themes of the articles here are the same and so are the fixes you can implement today: software freedom is a good unto itself because it helps grant you the independence and true ownership you seek, running free software on hardware you can fully own is the best currently viable way to get the independence you seek. The rest is a matter of political will—are you willing to change your system and hardware so you can have the best available hardware and software that respects your freedom? Wishing and hoping achieve nothing, real change requires political action.
I recommend perusing the GNU Project's list of free distros and the Free Software Foundation's "Respects Your Freedom" hardware list.
Digital Citizen
...if your firmware's up to date? I can find the version of the firmware that's installed. What I can't find is anything documenting what the latest version for my Mac is. Apple's support site is a joke.
Never let a lack of data get in the way of a good rant.
Give me the source code of the firmware, and allow me to install an upgraded version in my own time.
Buy your own copy of IDA Pro.
You now have the source code for the firmware.
You don't know how to program in assembly language?
Are you sure you are actually a programmer?
The length of time that some system has not been updated does not alone provide a good metric as to how secure it actually is or isn't. Its certainly a mistake to judge the invulnerability of some system just by when it was last updated, which seems to be what the article is doing.
It was Microsoft who managed to brainwash the world into thinking that weekly/monthly updates are just some normal aspect of all computer systems. prior to then, it was not unusual for updates for professional OS's (SunOS, HPUX, Solaris, VMS etc) to be more like years apart.
A high frequency of updates is absolutely necessary if you're running a fundamentally crappily-designed OS like Windows, but let's not paint all things with the same brush.
That said, I do agree that Apple should release updates every time a new exploit (EFI or otherwise) is identified, which the article also clearly mentions just isn't happening.
Not like anyone even bothers, any bugs in UEFI are only important if you have access to the hardware.
EFI bugs are important...
But only to 64 bit Linux users, who haven't commented out the call to ExitBootServices() which 64 bit Linux insists on making.
The bug, which exists in Intel's EFI/UEFI reference implementation build system, occurs due to not marking a section of one static library as "required by runtime services".
Apple EFI implementations have the bug; so do many other companies.
We fixed it at Google, with the help of the UEFI engineer on the H2O BIOS. Most people haven't fixed it.
So Linux people tend to get all pissy any time they can't update the EFI because they can't read disassembled assembly source and make modifications.
but one thing I see surprisingly frequently on the Surface Pro is EFI firmware updates.
Personally I'm waiting on the security update for the last Windows XP release...
I'm a little unclear why a bootloader would ever even be in a position to become 'critical'. Either it works, in which case the machine works and a real operating system takes over, or it doesn't, in which case the machine displays the ultimate in security and fails to deliver service to anyone, including malicious agents.
If bootloaders are now written to somehow be remote-hackable, we have done something very wrong.
UEFI displaces root kits by being one. It was inevitable to find a flaw in the code.
One of the great things about running Linux is the ability to run using BIOS only.
My PC BIOS is UEFI-only, you insensitive clod!
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
>Begin pedantic annoyance: If it's UEFI, it's technically not BIOS anymore.