WikiLeaks' New Dump Shows How The CIA Allegedly Hacked Macs and iPhones Almost a Decade Ago (vice.com)
WikiLeaks said on Thursday morning it will release new documents it claims are from the Central Intelligence Agency which show the CIA had the capability to bug iPhones and Macs even if their operating systems have been deleted and replaced. From a report on Motherboard: "These documents explain the techniques used by CIA to gain 'persistenc'' on Apple Mac devices, including Macs and iPhones and demonstrate their use of EFI/UEFI and firmware malware," WikiLeaks stated in a press release. EFI and UEFI is the core firmware for Macs, the Mac equivalent to the Bios for PCs. By targeting the UEFI, hackers can compromise Macs and the infection persists even after the operating system is re-installed. The documents are mostly from last decade, except a couple that are dated 2012 and 2013. While the documents are somewhat dated at this point, they show how the CIA was perhaps ahead of the curve in finding new ways to hacking and compromising Macs, according to Pedro Vilaca, a security researcher who's been studying Apple computers for years. Judging from the documents, Vilaca told Motherboard in an online chat, it "looks like CIA were very early adopters of attacks on EFI."
Nothing like good old BIOS and hardware jumpers
So UEFI is now a Mac only thing, huh?
It seems to me that having a chip, the management unit, in all intel processors that sits above even a hypervisor and can read all memory, have it's own connection to the network, runs java code, and is software reprogrammable, is basically the wet dream of root kits. it's invisible to anything you run on the CPU but sees all and tells all.
Some drink at the fountain of knowledge. Others just gargle.
And now maybee we'll know why it's been so hard for Open Source developers to get information on writing their own against-the-metal drivers for telephony radios and startup modules (BIOS, EFI/UEFI, etc.)
It has long been suspected that was not just proprietary info-walling, but to reduce chances of discovery of backdoors and persistent threats imposed in the name of spying.
Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
I've always transposed UEFI to UFIA in my mind. now I know why
Some drink at the fountain of knowledge. Others just gargle.
Prior to this, I'd have thought America and especially its government agencies do not hack.
I guess I was wrong. What troubles me is that the media only talked about the Russians, yet the act was taking place in our backyard!
Question: Will the media put both the left and right to task?
For remote management of OS startup/shutdown and system monitoring and its effectively a small seperate computer. I don't think consumer machines have this installed. Unless I'm getting confused about what you're referring to.
To bad you can't get to the UEFI / BIOS menus on a mac to be able to change boot keys.
This even made it into an episode of "Person of Interest" during its last season - although in that case I believe it was a criminal syndicate adding code to the EFI before the computers were shipped. Oh wait, I guess it was exactly the same after all!
#DeleteChrome
Note that both of these hacks require physical access.
Obligatory: Intel CPU Backdoor Report
Intel CPU Backdoor Report (Updated Mar 13, 2017)
The goal of this report is to make the existence of Intel CPU backdoors a common knowledge and provide information on backdoor removal.
What we know about Intel CPU backdoors so far:
TL;DR version
Your Intel CPU and Chipset is running a backdoor as we speak.
The backdoor hardware is inside the CPU/Bridge and the backdoor firmware (Intel Management Engine) is in the chipset flash memory.
30C3 Intel ME live hack:
@21m43s, keystrokes leaked from Intel ME above the OS, wireshark failed to detect packets.
[Video Link] 30C3: Persistent, Stealthy, Remote-controlled Dedicated Hardware Malware
[Quotes] Vortrag:
"DAGGER exploits Intel's Manageability Engine (ME), that executes firmware code such as Intel's Active Management Technology (iAMT), as well as its OOB network channel."
"the ME provides a perfect environment for undetectable sensitive data leakage on behalf of the attacker. Our presentation consists of three parts. The first part addresses how to find valuable data in the main memory of the host. The second part exploits the ME's OOB network channel to exfiltrate captured data to an external platform and to inject new attack code to target other interesting data structures available in the host runtime memory. The last part deals with the implementation of a covert network channel based on JitterBug."
"We have recently improved DAGGER's capabilites to include support for 64-bit operating systems and a stealthy update mechanism to download new attack code."
"To be more precise, we show how to conduct a DMA attack using Intel's Manageability Engine (ME)."
"We can permanently monitor the keyboard buffer on both operating system targets."
Backdoor removal:
The backdoor firmware can be removed by following this guide using the me_cleaner script.
Removal requires a Raspberry Pi (with GPIO pins) and a SOIC clip.
Decoding Intel backdoors:
The situation is out of control and the Libreboot/Coreboot community is looking for BIOS/Firmware experts to help with the Intel ME decoding effort.
If you are skilled in these areas, download Intel ME firmwares from this collection and have a go at them, beware Intel is using a lot of counter measures to prevent their backdoors from being decoded (explained below).
Useful links:
The Intel ME subsystem can take over your machine, can't be audited
REcon 2014 - Intel Management Engine Secrets
Untrusting the CPU (33c3)
Towards (reasonably) trustworthy x86 laptops
30C3 To Protect And Infect - The militarization of the Internet
30c3: To Protect And Infect Part 2 - Mass Surveillance Tools & Software
1. Introduction, what is Intel ME
Short version, from Intel staff:
Re: What Intel CPUs lack Intel ME secondary processor?
Amy_Intel Feb 8, 2016 9:27 AM
The Management Engine (ME) is an isolated and protected cop
Buy Apple. It's the American thing to do.
-- Tigger warning: This post may contain tiggers! --
Are you people really stupid or just paid shill? Or you have some kind of weak mind that you just can't accept how bad things are?
You really need to look at reality more before talking out of your ass, they've got you by the balls.
I just updated the report:
7. Active Intel ME Example:
Thinkpad X201 has KVM and Anti-Theft (internal 3G) enabled by default
intelmetool -s
ME: Firmware Version 0.996.511.0
ME Capability- Full Network manageability - ON
ME Capability- Regular Network manageability - OFF
ME Capability- Manageability - ON
ME Capability- Small business technology - OFF
ME Capability- Level III manageability - OFF
ME Capability- Intel Anti-Theft (AT) - ON
ME Capability- Intel Capability Licensing Service (CLS) - ON
ME Capability- Intel Power Sharing Technology (MPC) - ON
ME Capability- ICC Over Clocking - ON
ME Capability- Protected Audio Video Path (PAVP) - ON
ME Capability- IPV6 - ON
ME Capability- KVM Remote Control (KVM) - ON
ME Capability- Outbreak Containment Heuristic (OCH) - OFF
ME Capability- Virtual LAN (VLAN) - OFF
ME Capability- TLS - ON
ME Capability- Wireless LAN (WLAN) - OFF
It is pronounced as "You Effy" so it rhymes with your friend's Jeff's name when he was a kid (Jeffy) ... as in , hey You ... Jeffy ... come here. So no, it does not rhyme with Goofy.
If a computer tech has told you that it makes his job more difficult then said computer tech is an incompetent moron.
As far as your claim you don't seem to understand how the optional Secure Boot facility would stop this attack cold in it's tracks. With UEFI you CAN fight such an attack. With BIOS you have no such capability to protect against boot sector viruses, etc. Your post is nothing but ignorant claims about technology you don't understand, so much so that you don't even know how to pronounce the technologies name.
Is UEFI perfect? Of course not. Is it the best possible solution? Of course not. Is it better than BIOS? Hell to the fscking YES.
Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
Pretty much fuck you.
UEFI has greatly complicated everything it touches that I run into professionally, because it has turned stuff that had a reasonably standard way of happening into a shitshow of different custom crap, stupid shims, etc. Legacy OSes get confused, so it seems mostly tuned towards the applications that use the latest and greatest stuff. Sometimes you have to try out numerous combinations where the firmware treats some components as legacy BIOS and others as UEFI. The machines take longer than ever to boot, which I'm not sure is related to UEFI, but seems to have started around the same time.
All this from a product that was supposed to make stuff simpler!
Bitching about boot sector viruses is a dumb joke. BIOS just boots what you give it. If the BIOS isn't writable, then you can be sure your virus is gone if you just take out all the writable parts. With UEFI, you can have a FIRMWARE VIRUS that is literally and completely impossible to detect or remove. UEFI's ability to only launch a signed shim thing only inconveniences me, while creating an entirely new low level exploitable place that you can never trust- that is actually the point of this news article, after all.
UEFI is more capable, and slowly becoming standard enough. But it is still a mess that allows a new infection vector, a new place to store viruses, and somehow tries to be more secure by giving only Microsoft a signing key that everyone else has to beg for. There's a lotta backwards decisions in UEFI-land.
Hacked in shipment. The product line arrives altered as shipped, sealed and new to the interesting person.
A step away from the junk as designed or setting a junk international standard idea of the 1950-80's. The classic backdoor, trap door design.
The crypto can be examined and passed by outside experts. The product that then arrives as a random shipment is altered junk.
The data is then collected in person later, or from a normal network.
Domestic spying is now "Benign Information Gathering"
Re "Except you can monitor network connections."
AC thats why the later data collection is often done in person.
The code can outlast any rebuild, reinstall. Its more about been nice place to hide rather than needing a network out connection that will show in any log.
Domestic spying is now "Benign Information Gathering"
EFI and UEFI is the core firmware for Macs, the Mac equivalent to the Bios for PCs.
Not just for Mac's: All current PC's use UEFI - instead of BIOS - as well as Mac's do.
Newer versions are turning out to not allow bios disablement. The sad history of this, from what I can peice together is that initially you could disable it in bios. Then newver versions had "hidden" bios diablement. that is to say, no GUI bios diablement but still an editable firmware disablement. Then newer still ones, no possibility to disablement. For these some people have discovered that overwriting certain blocks (basically all blocks after the first block) of this allows disablement without the 30 second shutdown. One can see where this is headed in the next generation very easily.
Some drink at the fountain of knowledge. Others just gargle.