Malware Exploiting Spectre, Meltdown CPU Flaws Emerges (securityweek.com)
wiredmikey quotes SecurityWeek: Researchers have discovered more than 130 malware samples designed to exploit the recently disclosed Spectre and Meltdown CPU vulnerabilities. While a majority of the samples appear to be in the testing phase, we could soon start seeing attacks... On Wednesday, antivirus testing firm AV-TEST told SecurityWeek that it has obtained 139 samples from various sources, including researchers, testers and antivirus companies... Fortinet, which also analyzed many of the samples, confirmed that a majority of them were based on available proof of concept code. Andreas Marx, CEO of AV-TEST, believes different groups are working on the PoC exploits to determine if they can be used for some purpose. "Most likely, malicious purposes at some point," he said.
And release full memory dumps of all the computers in that company for everyone to see. Those little greedy dip$hits that created the issue with their cheating in the first place and who refuse to provide fixed goods to the wronged parties
If a researcher, tester, AV company sends some PoC code opening calc.exe, then this is not malware! To be malware, some code has to be actually malicious, doing evil things like encrypting harddisks for ransom, sending spam, mining coins, etc.. Simply trying out a bug in existing software to get a better understanding or to write AV detection routines is not malware!
Except maybe code from AV companies. That is probably always malware, no matter the intent or what it actually does
Did you really expect this massive, gaping security hole, that got a metric fuckton of media coverage, to go unexploited?
I am not saying that it is impossible to be exploited, but much more difficult than what so much advertisement seems to imply. Logically, I am more than ready to be proven wrong. Also I do think that all this should be eventually fixed, at least, under the most demanding/vulnerable conditions. Anyone willing to put together a small virus (not doing anything bad + source code, evidently) to prove me wrong?
Custom Solvers 2.0 = Alvaro Carballo Garcia = varocarbas.
Everyone, make sure your Faraday hats are grounded. Anyone consider that this news of all modern stuff being compromised and unfixable is just a ploy to force everyone to upgrade their hardware and software, so that the new backdoors become universal?
Well now well see just how good my AV is..I didn't patch im on win 7 ultimate upgrade from Vista full. It would be a HUGE PITA to recover lol but i refuse to go win 10. im not paying for an OS that forces ads on me or controls what i choose to install on MY hardware..you get the point...
Jack of all trades,master of none
this is a blessing in disguise: ... very little? and help keep the web ... saner : ]
disabling javascript in the browser should reduce the attack surface to
Get all passwords and documents you care about off the pc so there is nothing for spectre to read. The spectre attacks are not detectable so antivirus programs likely will not detect them. Running a secure Linux rather than Windows still might be the best hope, but not for attacks taking place through the browser. Perhaps have an "empty" machine with just a browser for internet connectivity and browsing/surfing.
Take the cheese to sickbay, the doctor should see it as soon as possible - B'Elanna Torres, "Learning Curve"
I know I'm a bad person for wanting to see the blood, but where are the fireworks?? I mean this is supposed to be the biggest, baddest, least-detectable, most-exploitable thing since rpc.statd and Sendmail! C'MON you Chinese commie pinko robot exploit h0x0xr army! Hit me with everything you got! To quote an old sage, "I'll tell you what you cocksucker. You try to hit me and I will kill you. Don't try to hit me."
Seriously though, has this not been the shit-talker-est set of exploits of the century? Where's the fire folks? In. The. Wild. They are already being reported and they don't seem to be doing 4/5ths of 5/8ths of fuck all. Oh, noes! They are going to dump my ring buffer! Call the president! Holy fuck! If it's that bad then do it through OpenSSH on an OpenBSD host or I call bullshit.
When I click the link it wants me to give them my email address before I can read the article. It cannot be any worse than Intel (ME )
The HP Z840 workstation BIOS has 3 menu layers to switch it off so it declares. But I do not believe it switches it off it hides it. When running the Intel-SA-00075 Detection and Mitigation Tool it says not vulnerable does not get a response from it. If I move clip 40 and switch on the machine BIOS flashes a message before booting about it being vulnerable and download the patch fix from HP.
http://oi67.tinypic.com/zwc5xl...
I'm strongly against the anti Russia fervor over the last year, but you can probably imagine exploits like this are a lot more concerning to people working inside a government or with security clearances, I'd also say those are the same people (vault 7) who are working the hardest and spending the most to incorporate this into their attack suites
Comment removed based on user account deletion
AMD considers their CPUs potentially vulnerable to Spectre Variant 2 - "Branch Target Injection". (The one were one attacker application is able to do it bidding into a completely different and innocent target application)
Some more recent AMD processors do indirect branch prediction.
But the way they do this indirect branch prediction is completely different.
Currently the Google demo code against Intel Xeon doesn't work (well, obviously).
Nobody has managed to write a successful exploit of that variant.
AMD engineer believe that it's a terribly difficult task that might not be doable.
So they might indeed end up being more or less Intel-specific-ish.
Sèectre variant 1 - "boundary check bypass" is the one affecting every CPU that those speculative execution and is basically "speculative execution working as it should/as documented, but now somebody has found a way to use it as a side-channel attack to have a software see its own data".
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
Serious question - or are we all at their mercy?
It sounds like AMD should come out of this quite well.
At least much better than the giant pile of mess that is Intel.
That's why some experts are pissed at Intel trying to muddy things and pretend all CPUs are equal.
(Nope. All CPU are equal in *Spectre v1* only.
Intel's peculiar way to optimize at the cost of everything else including safety and sanity stands out a lot in Spectre v2 and Meltdown).
I can't decide whether variant 1 sounds "possibly dangerous" or not. I suppose it depends on how applications segment their data.
Yup.
There's a reason why web browsers have moved (Chrome) or are moving (the whole reason to switch Firefox from XUL to WebExtensions is to enable Electrolysis by default) to multi-proc models. Eventually none of the critical data (e.g.: Password Manager extensions) and externally provided arbitrary code (Javascript on websites) will be living in the same process.
And there's a reason why the JITting of eBPF isn't enabled in the Linux kernel by default.
But I'm really skeptical about speculative execution in hyperthreads in any case.
Hyperthreading and speculative execution are completely orthogonal to each other.
They are two completely different strategies in answering the problem of how to keep the pipeline fed, each time it stalls (e.g.: while waiting for something to be fetched from the memory, or some long computation to finish).
You don't know what you should do next : ...so you make your best guess, and try to do it anyway. If your guess turns out right, you're gaining some execution speed. ...but there are N other task currently wait for which you DO know what to do next. Do them instead.
- Speculative execution :
- Hyperthread:
Speculative execution comes at lots of complexity (in order to be able to invalidate wrong turns) with devil lurking in the implementations details (side-channels, security checks done too late).
Hyperthreading is much closer to normal execution and simply require doubling some already existing facilities in order to enable the CPU tracking N tasks.
OTOH, given the way applications are currently written, I can see why they did it, I just think it's a poor local optimum.
Hyperthreading is the *better* solution... except that, for it to work, it requires to have N other tasks in the wait.
Hyperthreading works better in heavily multi-tasking use cases. So you'll find it on servers (typical server-only CPUs like the UltraSparc Niagaras had 8 threads per CPU core) and on GPUs (as anyone used to CUDA knows, the basic strategy is keeping as fucking many threads in flight as possible).
It works on task which are heavily parallel (tons of servers and daemons, or tons of pixels, etc.)
But it doesn't help on task that as mostly single threaded so it doesn't look nice on lots of benchmarks (e.g.: older games, lots of compression tasks).
In other words, Multithreading won't make your Windows go faster (Even more so as Windows has traditionally lagged behind the starte of the art process schedulers).
"Local optimum" as you say.
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]