Also just because some information got leaked, doesn't mean that there aren't more units / projects at the CIA where maybe the more skilled people are working and where the "good" attacks don't get leaked.
This looks to be the kind of stuff for the day in, day out operations.
Creating antibiotic-resistant bacteria is a bad idea. Don't use linezolid when you could use vancomycin.
Don't use your fancy rootkit if the boring DLL injector you give the contractors works just as well.
If I were CIA in the current political climate, I would simply slightly modify a Russian exploit toolchain and exfiltrate data to CIA controlled C&C. One dev can do the work and with a couple of days of effort it would get past all major AVs.
Creating this sort of malware isn't expensive, so why not do it.
There's a big difference between broadband spray and pray malware, and malware you actually want to hit a target with.
If you know average tools won't detect it, then why get fancy when you have something that's proven reliable and if discovered is unlikely to have your victim substantially improve their processes?
Also, the hextuple-agent in me wants to think the simple exploits were leaked intentionally to distract from the whatever-else-it-is-they-don't-want-you-to-know.
I don't want to rush to judge them because not everyone can be at the top and if it works it works. If I can pop a box using powershell, it's way easier than having to develop some kernel level hack. Additionally when anyones 'private' conversations get leaked they always look like a fool because it shows us being vulnerable and asking dumb questions, but a lot of the posts really do remind me more of the sysadmin who learned some python instead of the cutting edge of private industry.
There's two ways microcode goes on Intel CPUs. The first is when it gets flashed in at the factory onto an OTP ROM. The second is when it gets uploaded to a block of internal RAM by your computer, every time it boots. That's why packages like this one (https://www.archlinux.org/packages/extra/any/intel-ucode/) exist.
One is set at the factory, one is set by your computer every time, once at boot, before the completion of boot. Also, it's very carefully signed, so even if you managed to put a bootkit before the OS boot, you would need to steal Intel's microcode key.
Microcode is not targetable. Few things at that level are. (A decent example of something that might be more targetable at that level is a hard drive controller. Less difficult but still not easy.) The amount of engineering needed to pull off an exploit that is "99.9% chance" unnoticeable, but still persistent, is much more than that of a "99% chance".
(I know nothing of AMD's CPUs and their microcode, but I'm guessing it's much of the same.)
Scenario 1: Supply chain interdiction. You don't need to target the CPU only after it has been manufactured and put into whatever you want to hack, you can start way earlier, including at the factory.
Scenario 2: Getting the signing keys from hardware manufacturers, including Intel, seems quite feasible for state actors. You don't even need hacking (I assume Intel's keys are kept air-gapped) or relying on secret court orders, plain old spycraft would probably do the trick.
That said, my argument can be rephrased to consider the hard-drive controller or other peripheral firmware rootkits instead, if you prefer and care only about scenarios where the rootkit must be delivered over the network to a clean system without attacking the CPU manufacturer.
It was a big deal at the time known as "l'affaire gemplus" and it prompted the french government to set up the "Fonds stratégique d'investissement" or strategic investment fund, sort of a french in-q-tel.
Intel being a US company it is probable the US agencies have their ways with them.
This is why I run libreboot and I neutralized the IME by flashing my BIOS using SOIC-8 chip clips and a Bus Pirate.
I guess I'm paranoid.
I guess you refer to a procedure as described in
https://hardenedlinux.github.io/firmware/2016/11/17/neutrali...
I would say what you did is to "neutralize" the ME firmware part in the flash BIOS. But this is only firmware that the ME loads additionally to load applications like e.g. AMT. The ME has it's own internal ROM containing it's very own firmware which is inaccessible and can not be modified.
So what you have is libreboot running on top of a still functional IME. All you gained is, that you got your BIOS of choice installed, and to remove some ME apps from the flash image. Correct me if I am wrong.
I'd expect a microcode-level rootkit to run a five-nines success rate evading detection unless used against someone who's paranoid enough to have _something_ in place to detect it, and I'd venture further that the 3LAs of the world are smart enough not to target the infosec-paranoids of the world.
Admittedly, the best rootkits probably target the network equipment as well as the host.
At the host level, most organizations wouldn't be able to detect an unmasked trojan running as its own separate user process unless its signature was already known or its behavior caught by a blacklist-based IDS.
Also rootkits are way overrated. What you do when you compromise an organization is you open a connection to your C&C on a few machines to keep your foothold if any reboot. If you need to get in you just connect to one of those boxes and just continue on. You never have to drop anything on the hard disk which makes it much stealthier.
fair enough, but the like the person above said, it can be very important to hide/obfuscate the identity of the snooper. Stuxnet would have been more effective if experts could not immediately point to US/Israel.
On the other side, there's an organization that by definition asks you to take them on their word that everything they good is for your own good...
Of course WikiLeaks wants ordinary people to be vaguely afraid of using Signal and WhatsApp. End-to-end encryption is very much counter to their goals.
I don't trust signal, a centralized that requires a phone number while pretending to be secure and providing some anonymity is flawed by design and begging to be exploited.
http://technosociology.org/?page_id=1687
Get off the FUD brigade.
FWIW, I strongly disagree with this stance: if the recipient's key changes while the message is in-flight, that message should never be resent/delivered without the sender's explicit approval. Imagine that Bob is a political activist planning a protest. Bob is wondering why his IMs to a co-conspirator Alice aren't being delivered; Bob's wonder turns to fear when he hears on the news that Alice has been detained. Fear turns into terror when Bob sees his messages subsequently get two blue ticks as WhatsApp happily delivers his IMs to a new phone belonging to the secret police. Only afterwards does WhatsApp notify Bob that Alice's key has changed
> Wasn't whatsapp all over the news for its "replace the encryption key transparently without notifying the user" feature ? Also facebook.
Which was a conscious design decision. Not doing that (even for people that had turned on "notify on key changes"), would let whatsapp know which users could be securely MITM'd. Neither is a very good choice, but an understandable trade-off when it comes to security vs usability.
You can do lots of things when you've owned someone's phone. The big news is that they're targeting phones instead of services.
Given that, it's very peculiar to focus on the services WikiLeaks wants you to be afraid of anyway, when they're mentioned nowhere in the documents.
What would those goals be?
Release it and let people figure it out or shut the fuck up.
Snowden is a hero. Assange is an asshat.
https://theintercept.com/2016/05/16/the-intercept-is-broaden...
Also Assange would be Poitras/Greenwald here not Snowden.
::: THIS ARCHIVE FILE IS STILL BEING EXAMINED BY WIKILEAKS. :::
::: IT MAY BE RELEASED IN THE NEAR FUTURE. WHAT FOLLOWS IS :::
::: AN AUTOMATICALLY GENERATED LIST OF ITS CONTENTS: :::Find a better justification for your beliefs.
The CIA works abroad, not on American soil, so none of these tools are being used against the American people anyway (thats the NSA's job). I imagine this is part of a network or "library" of exploits they have, in case they encounter say a North Korean laptop with Windows 98 and they need something in a pinch.
>doesn't mean that there aren't more units
Exactly, thats why they call it a "leak" and not a "turn the hose on full blast."
I don't think you can underestimate how stupid these big bureaucracies can be.
But never underestimate your opponent, and all that...
Actually the vault7 leak is the first in a series and it is clearly stated that this is only a portion of the CIA tools:
> Recently, the CIA lost control of the majority of its hacking arsenal including malware, viruses, trojans, weaponized "zero day" exploits, malware remote control systems and associated documentation. (..) The archive appears to have been circulated among former U.S. government hackers and contractors in an unauthorized manner, one of whom has provided WikiLeaks with portions of the archive.
Edit: Maybe someone can answer this question for me.. So from the Snowden leaks, we know the extent of the NSA toolkits and the requirements which need to be met to utilize them. Now we know some of the CIA's capabilities, and after Apple refused to unlock the San Bernardino Shooter's iPhone, we found out the FBI was playing some sort of politics, by claiming that justice might not be served without Apple's intervention, and proceeded to publicly shame the ethical position Apple took. So why on earth was Obama trying to force Apple's hand in that matter? Soon as Apple said no, the FBI somehow found the single magical person willing and able to defeat the privately enhanced security of the shooter's 5S? Makes no sense to me.
The most interesting tool I found in the leaks was the bug that jumps airgap to make Nero burn trojaned binaries. If we see more tools like this come out of the woodwork, it shows that the CIA is at least in some ways keeping their teeth sharp.
I believe that the FBI and Obama both played politics for a few reasons, namely:
- Obama and the FBI probably withheld a reasonable amount of information from each other regarding the case
- This was all a charade to bring the topic into the public sphere. It backfired, but the aim was to allow future high-profile cases on which concurrent evidence trails are harder to establish. Once it backfired, Comey came out with a public letter admonishing the American people, comparing us to children. He stated that with Rule 41 coming into effect, the FBI would use its expanded powers to collect information for the following year. They would then use that information in an upcoming "adult conversation" the FBI wishes to have with the public about the future of open, libre encryption.
We should be expecting that "conversation" to take place this year. And I don't expect it to be much of a dialogue so much as a monologue. I expect the FBI to either directly or indirectly (thru Wikileaks, etc) release information that "proves" that backdoored encryption and its inherent reduced security is necessary for public safety. There is a saying we all know and love about the merits of this particular trade-off
I'm certain the FBI always had that contact on standby. They probably received multiple unprompted bids from various hacking companies during the public run of the case. They wanted to flex how much pull they had over a giant like Apple. Even though they seemingly failed, they came out with a huge data point: The American people need further brainwashing and ideological shifting before attempting a full coup over libre encryption in America.
I hope that things make a little more sense now.
/puts on tinfoil hat
There is also the other option which is that trust in American tech companies has been sketchy at best following the NSA leaks and this was a chance for the Obama administration to allow companies to reestablish some legitimacy when it came to security by making the US government look evil but having the corporations 'prove' that they are not backdoored by the NSA. They can still break in the covert way, but it makes it look tech companies are not as compromised as the NSA leaks would suggest.
they might also used the whole stunt as a way to inform the public that they have the capability so that next time around at the interview goes "look kid, we do have the capability to unlock the phone, but it's costly, nasty, annoying for everyone involved and will put your refusal in a very very bad light in front of the judge and jury, why you don't just give the code and we tell the judge you cooperated?"
Edit: https://leaksource.files.wordpress.com/2013/12/nsa-ant-ragem...
The FBI --- our domestic intelligence agency --- has been doing kernel keyloggers since at least 2003.
All speculation, of course.
Simple attacks are often (sadly;still) the most effective.
Some of the most talented software engineers in the world work intelligence, and they can write better than you, exploit faster than you, debug more thoroughly than you, etc.
State intelligence is especially dangerous and devious. The average security researcher doesn't stand a chance, much less the average basement hacker.
Understanding what the CIA does and why they do it is designed to be more or less impossible from the outside. It's the nature of intelligence really, to be incomprehensible from outside the sphere.
I read the Snowden leaks. I know what type of tools they're using. I know the type of holes that their public facing infrastructure has. I know the type of holes that their government officials that they're supposed to be protecting have. I know how fucked the security environment is right now. The CIA doesn't even use HSTS or CSP headers for fucks sakes (lol, they get an F on observatory.mozilla.org) so we are not dealing with an organization of godlike power.
These people work in a bureaucracy. Some of them are geniuses that write stuxnet or break HTTPS ciphers, most are not. Most are dll or SQL injection kiddies. Or they use grep to filter emails.
I didn't mean to insult your prowess or whatever, but people gotta understand the level that they operate at. It's insane
I don't think there's much more to the CIA than what's in these leaks. To do anything more, you'd need tens of thousands of people and huge server farms. You can't hide that stuff.
I truly doubt this for a multitude of reasons, but pay alone suggests otherwise.
http://www.nytimes.com/2007/07/22/books/review/Thomas-t.html
> new cuck times
Hell no.
I'm very familiar with business intelligence, and I'm somewhat familiar with govt intelligence though I've never actually filled a contract or anything, I've spoken with plenty who have, and have worked with a few as well.
The intelligence universe is completely parallel to the rest of the world. People just don't get it.
For the other 20% of targets who are serious about security (High-level government actors in countries that can invest a lot of money into serious computer security.) The CIA probably has a bunch of high-level tools that were not leaked.
Could you expand on why you feel the CIA in particular would have high-quality remote exploitation capabilities? Assume a talented hacker wants to join the government. Why would they choose to work for the CIA and not the NSA or the FBI?
I'm not saying the CIA does second-rate work in general, but perhaps their remote access work is second-rate in comparison to the NSA/FBI and to the very talented echelons of the private sector.
That was exactly the vibe I got from the leak as well. I don't know why people are going crazy over this, thinking Notepad++ or all Samsung SmartTVs are backdoored.
Who knows, maybe LD_PRELOAD is also an amazing method to hack programs?
Got to have something to spend the budget on to ask for more next year?
Maybe they are just trawling and they have more skilled people pick out the wheat from the chaff or combine exploits. It would make sense if there are some bigger picture people directing the contractors. A library of low-level shit might be useful if you're building entire frameworks.
Silt builds up at classification boundaries. You should expect to see a bunch of S crap that can't get to the TS tools, TS crap that can't get the compartments needed for the great tools---all in service of not devaluing the tech.
This was the U silt pile.
DLL injection seems like a perfectly fine hammer in the toolbox for that purpose. Nobody is claiming that they are using it for anything more than targeting specific applications once they have already gained system access. How they got that access might make for more interesting documents.
The CIA is in the business of obtaining information, not malware research.
What's impressive about things like Stuxnet is the amount of work and coordination it must have took to make it. The actual techniques were rather unremarkable.
Didn't Stuxnet involve backdooring Siemens PLCs? I find that pretty remarkable. In general, extremely sophisticated exploits that target critical infrastructure require attacks that haven't already been considered, be it for delivery or execution.
Are you calling Notepad++ or the CIA silly, here?
If the first case (which I assume) you're comically missing the point yourself, which is a big middle finger to a hostile government agency. This is an international Open Source software, used worldwide, that has taken a stance against US politics before (export restrictions).
So yeah maybe it is to embarrass the CIA, but not quite in the way you describe.
By publicly releasing this "fix", they're making a noise calling out LOOK WHAT THE CIA IS DOING PEOPLE, instead of shrugging "eh, is that all, I sure hope they got better exploits from my tax money" and "gosh I wonder why whoever released all this is angry with the US or something, I bet it's cause they're biased".
Now there's a public post on their site, on record, being shared everywhere that says BUGFIX BECAUSE THE CIA ACTIVELY TARGETED OUR SOFTWARE, so that people know this is no longer some "'They' could potentially do X and Y" but that it's actually happening and in this particular case "They" are the CIA.
I think you understand perfectly well how this sends a very different message to a very different (broader) audience than the (admittedly much more serious) revelations at Blackhat conferences. You remember that all these serious capabilities have been around for a long time, but the public didn't really take it seriously because many people believe "they wouldn't really" or the attacks were surely theoretical or otherwise we'd hear more about it, right? Or even when the capabilities have been right there, clear as day, for a decade, to actually assume "They" are really listening on your Samsung Smart TV's microphones (or you name it), has been flat out conspiracy nut territory or at best you could say "surely they only deploy these capabilities on a very small, targeted scale, responsibly".
And now they're not. We know it's happening. New proof of new scandalous breaches of privacy of individual indiscriminate members of the public comes out every other month or so. The whole world knows that the US/UK surveillance apparatus has spiralled out of control and is surveilling, spying and collecting data on everyone, everywhere. To say now, let's not make a big deal out of this because it just confirms what everybody could have known all along, is an idea that should have its motives questioned (by which I mean, you should maybe ask yourself, not that you're doing it deliberately).
Does Notepad++ really believe that with this fix they've successfully defended their software against CIA (or other gov.actor) exploits? Of course not. But they do get to make a big fuss out of it. And that's important too. If the police beat you up, is that something to make a big fuss out of and try to fix and make sure they don't get away with, even if it doesn't help with them still getting away with actually shooting people dead elsewhere? You can argue about that, but I wouldn't call it "silly".
Are there now people who will think "phew at least now Notepad++ is protected against CIA hacks"--well, probably, quite a few. But you're not addressing or helping those people by talking about Blackhat and hypervisor rootkits.
(... and if it's the second case, "silly" is a bit of an understatement given what these people have been up to the past half century or so--it's not actually quite as funny as in the film Burn after reading)
Sticking with the CIA, though, let's say we apply the bill of rights in its most stringent interpretation; then the CIA can't hack into anything that any American might use to communicate to, without an American warrant. That would be totally unrealistic, and the result would be no tech toys for the CIA. They would be at a significant disadvantage compared to other intelligence and manipulation agencies around the world.
Or perhaps another spin on it... does the Bill of Rights apply in the case where an ISIS combatant is firing on a US Marine, where the combatant happens to be an American? The Marine won't know that, and will treat them as a combatant. The Bill of Rights doesn't seem to apply in this case. Given that to be the case, then should the Bill of Rights apply where the CIA is hacking into equipment that a non-American is using and might use to communicate with an American?
But they (US+UK) are, agencies that have been allowed natural access to the infrastructure and resources required to implement surveillance on such a global scale. So much so that other intelligence agencies are making deals to get access via them. So, say, the Dutch AIVD, they don't have the majority of Internet data flowing through their territory (with nearly all large tech companies being US, clouds, browsers, software etc) so they can't directly abuse this access, because their scope is limited, unfortunately they can still trade for it because we have two nice big ports with transatlantic Internet cable connections (unless we already traded US access to those for something else, I don't know). So sure, they're being bad, but they're also limited, and they're not the root of the problem.
The US and the UK are in a very unique position for global Internet surveillance.
If Notepad++ wants to push an update that fixes DLL search paths purely for symbolic reasons, so that all their users are aware of what the CIA is doing by seeing the changelog, that's another thing entirely, and yes, I agree that's useful.
Of course it is. Notepad++ is an international project and these reasons are exactly why I upvoted this story.
(I'm honestly a bit confused as to what other reason one could come up with that is not an insult to Notepad++ developers' intelligence--"There, we fixed the DLL inject-y thing, finally now our users will be safe from CIA hacks"??)
Here's the rootkits track from Black Hat 2008 --- keep in mind that this is almost a decade old and that it's public work:
* Deeper Door: Exploiting NIC Chipsets
* A New Breed of Rootkit: The System Management Mode Rootkit
* Insane Detection of Insane Rootkits
* Crafting OS X Kernel Rootkits
* Viral Infections on Cisco IOS
* Detecting And Preventing Xen Hypervisor Subversions
* Bluepilling (implementing a hypervisor rootkit) The Xen Hypervisor
This is just one year's work. If you summed all of it together, you're talking ~2.5 FTEs across 7 different research projects which we will very generously assume took a full year to develop (spoiler: no, none of them did). People who can write hypervisor rootkits command a pretty decent salary, but it's not 2x the prevailing SFBA senior salary. So this is at most mid-single-digit millions worth of work.
I don't know why the CIA has this team of people bumbling around with DLL injectors and AV bypasses. Maybe it's some weird turf thing they're doing against NSA? But the stuff in the CIA leaks is not the standard you need to be protecting yourself against.