Google and Microsoft Disclose New CPU Flaw, and the Fix Can Slow Machines Down (theverge.com)
An anonymous reader quotes a report from The Verge: Microsoft and Google are jointly disclosing a new CPU security vulnerability that's similar to the Meltdown and Spectre flaws that were revealed earlier this year. Labelled Speculative Store Bypass (variant 4), the latest vulnerability is a similar exploit to Spectre and exploits speculative execution that modern CPUs use. Browsers like Safari, Edge, and Chrome were all patched for Meltdown earlier this year, and Intel says "these mitigations are also applicable to variant 4 and available for consumers to use today." However, unlike Meltdown (and more similar to Spectre) this new vulnerability will also include firmware updates for CPUs that could affect performance. Intel has already delivered microcode updates for Speculative Store Bypass in beta form to OEMs, and the company expects them to be more broadly available in the coming weeks. The firmware updates will set the Speculative Store Bypass protection to off-by-default, ensuring that most people won't see negative performance impacts.
"If enabled, we've observed a performance impact of approximately 2-8 percent based on overall scores for benchmarks like SYSmark 2014 SE and SPEC integer rate on client 1 and server 2 test systems," explains Leslie Culbertson, Intel's security chief. As a result, end users (and particularly system administrators) will have to pick between security or optimal performance. The choice, like previous variants of Spectre, will come down to individual systems and servers, and the fact that this new variant appears to be less of a risk than the CPU flaws that were discovered earlier this year.
"If enabled, we've observed a performance impact of approximately 2-8 percent based on overall scores for benchmarks like SYSmark 2014 SE and SPEC integer rate on client 1 and server 2 test systems," explains Leslie Culbertson, Intel's security chief. As a result, end users (and particularly system administrators) will have to pick between security or optimal performance. The choice, like previous variants of Spectre, will come down to individual systems and servers, and the fact that this new variant appears to be less of a risk than the CPU flaws that were discovered earlier this year.
Or perhaps that's just the skeptic in me talking.
After all the speculative execution flaws are found and fixed (in hardware or software) the question won't be how much of a slowdown those fixes cause, but how much of a speedup from speculative execution remains.
Corruption is convincing someone that the selfless ideal is the same as their selfish ideal.
... Security or Performance.
Not everyone is a gamer, video editor, etc.
Many people would gladly sacrifice 50% CPU performance, in exchange for more secure and stable processors.
But Intel and its OEMs are reluctant to even give us consumers the choice to obtain decent microcode security fixes that slow down our computers too much.
Intel already provides the NSA with the ME backdoor, so why won't they at least try harder to close the other security holes?
SHUT EVERYTHING DOWN.
Install security patches?
Turned off windows updates years ago and never looked back, running ad-block/webmail removes most attack vectors anyway. I've never seen a lot of value in patching already known flaws, at the end of the day it's a zero-sum game.
And my professor laughed when I held the single-cycle CPU design to be the holy grail of the industry...
AI techniques and advancements should be be able to correct all negative side effects and performance hits in the very near future.
When Palladium failed to catch on like they wanted, a series of difficult to exploit bugs started being pushed into tech. Once Intel ME, ARM Trustzone and similar were in place, as permanent methods of user-control lockout and backdoors to the encryption keys/code running on the system, all they would have to do is release the ignored/well hidden exploits to the public and use them to kill off the last generations of processors of sufficient performance that still empowered the user.
Cue today: That is exactly what has happened. 10 years of processors with code signing that the owner of the hardware doesn't really control or own. Serial numbers on every item in the system that can be used to fingerprint the users system to such a scarily high degree of accuracy once will have few chances to remain anonymous under normal usage conditions.
The dangers of the future are here today, and without a large and collective financial push by us little guys, the final opportunity to rebel against technological enslavement will be lost, resulting instead in ever dwindling puddles of tech rebelliousness that will be inexorably quashed out, one at a time until all that remains is a bunch of dry lake beds surrounded by technological dystopia.
How do I get a refund for being sold a defective product?
Seriously, how are continuing issues with the same CPU or software not covered by some sort of lemon law?
The benchmark sites need to start using or disclosing speeds with the "feature" turned on.
Some drink at the fountain of knowledge. Others just gargle.
Hillary will die in prison.
I have for most of my life assumed processors had an infinite well of side channels vendors have not the will to ever address with exploitation of cache/prediction schemes being obvious.
I know for a fact people have been talking about this for decades. You can find publically available examples as this 2006 article attacking RSA using branch predictor side channel. https://eprint.iacr.org/2006/2...
Then we have all of the Power/RF tempest crap.
Vendors should address this with a holistic secure design rather than endless piecemeal drip drip drip of look what I found lets slap a label on it and slow shit down even more.
Vendors releasing unreliable code that makes things worse. Or solutions requiring new BIOS updates that manufacturers won't bother pushing or users won't bother installing leaving a bunch of people randomly vulnerable. The piecemeal reactionary approach sucks ass.
When this is all done and dusted I will be left with a z80
Kids, do not fight. As a compromise, they will both be put in a box together. Then they will fight to the death. To make things even, Hillary will get a screwdriver.
The really are the better option atm.
As it seems from all three big archs (ARM, Intel x86, AMD x86) amd seems to be the least affected due to their design.
And also for the time being they seem to be the nice guys, first their boards last 4 processor generations
secondly, their processors kick ass and kick Intels ass in most real life scenarios and have a fair price. It is about time that more people buy their stuff. Ryzen and AMD
really deserves it.
> The firmware updates will set the Speculative Store Bypass protection to off-by-default, ensuring that most people won't see negative performance impacts.
Devices will remain insecure by default to protect our brand image and shareholders. How the f* do you think it is a good idea to set a security patch as off-by-default?
So, in the future CPU makers don't need to invent new names. We'll just identify CPUs with the name of the newest vulnerabilities they have :) it'll be much easier :)
I am putting myself to the fullest possible use, which is all I can think that any conscious entity can ever hope to do.
i8086 ... ...
i8080
i80286
i80386SX
i80486SX
i80486DX
Pentium
Pentium II
Pentium
Xeon
Can anybody explain us why are there many CPU names/families in short time?
Moreover, If these chips are vulnerable and have hidden backdoors then many enterprises do question how make safe/sure/trust their systems?
Intel/AMD/Apple chips are not the solution. They will look for another solutions.
This time it depends on both the CPU and the OS.
This is basically a "read-after-write" situation, where the CPU tries to speculate before the write is actually known.
Depending on your CPU + OS combo, this will be limited to data you already have full read/write access to anyway.
(AMD doesn't speculated pass memory protection, Intel does(*).
Linux use a copy-on-write memory allocation scheme, that grantees that all memory page seen by an application are magically pre-filled with zero, meaning that an application can never(*) see some other application's remaining data. But other OSes may differ - I have no idea and don't bother enough to check).
So on AMD arch + Linux OS, all you're ever going to see it is the apps own (non overwritten) data.
(Well unless there's a new "kernel stack information leak" that gets discovered - basically the kernel leaving dangerous stuff lingereing on the stack)
So it mostly affect situation like browsers where 3rd party provided code (eg.: internet downloaded javascript) could run in the same process context as some critical bits of information (say a password management plugin).
It should not effect kernel or hypervisor.
---
(*) + (*) I'm almost ready to bet that somebody will find discover an intel-specific exploit to speculatively execute around page faults.
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
"Safari, Edge, and Chrome" - but where is Firefox? Then also Chromium but that is assumed to be patched along with Chrome. Nobody cares about Free software anymore?
All the screwdrivers in the world won't help her when Trump grabs her by the pussy.
"Prediction: within 10 years, Windows will be a Linux distribution." Me, 7-6-2016
WARNING: this link goes to domain squatting malware shitware, not a graphic pic of a horse-fucker stretching out his anus. You may be disappointed.
"Prediction: within 10 years, Windows will be a Linux distribution." Me, 7-6-2016
Touch decision... how to decide?
Linus rant incoming in 3.. 2.. 1..
Zing!
Planned obsolescence at its best.