Posted on 01/03/2018 1:55:39 PM PST by Red Badger
The fix requires major OS rewrites which will probably make your computer run slower.
An extremely severe security flaw has been found to affect nearly every Intel processor made in the past decade or more, giving any hackers who might know how to exploit it access to protected information systemwide. The Register reports that programmers are rushing to make the sweeping changes necessary to protect against the vulnerability on Linux and Windows operating systems, with such fixes required on macOS as well. Even worse, you can expect these vital updates to noticeably slow down your computer.
The design flaw in Intel's x86-64 hardwarefirst introduced in 2004 and still in use in the lion's share of modern-day processorsallows programs without the proper permissions to access the part of an operating system known as the kernel, a low-level chunk of code that controls literally everything in your system.
The exact details of the vulnerability are still somewhat under wraps, but as The Register has pieced together from multiple, technical sources, it appears the flaw is based in a feature called "speculative execution." This trick allows a processor to do things before it's absolutely sure they need to be done, so the results are ready as quickly as possible if needed and simply ignored if not. In Intel's x86-64 hardware, however, it appears that programs may be able to speculatively execute code they would not have permission to run under normal circumstances, allowing carefully-constructed, malicious code to essentially read your entire operating system's mind without the proper permission. The potential bounty of such an attack includes passwords, login files, and pretty much anything you'd ever want to keep secret.
It's hard to zero in on the most troubling part of this flaw. Intel's x86-64x processors are the most widely-used chips in virtually every form of laptop. If you don't know what processor you have, you almost certainly have one with this flaw. If you do have an AMD processor, however, congratulationsthey are confirmed to be safe from the exploit.
In addition to the ubiquity of Intel processors, the low-level nature of this vulnerability means that hackers who may have learned to exploit it would have access to an unprecedented number of machines. And considering x86-64 has been around and prevalent since 2004, possible hackers have had access for over 10 years. No researchers have yet come forward with an example program that exploits this flaw, but that's hardly proof that hackers, or the NSA, didn't figure out how to make use of this exploit years ago.
On top of it all, the fix requires extremely deep and wide-reaching changes at the root levels of an operating system's softwarechanges that could impact performance of Intel machines by as much as 30 percent. The only alternative? A new computer with a different processor, or one powerful enough to make up for the performance hit. Even worse, these performance hits won't just come to your computer, but also the army of distant servers that run countless internet-connected services in the cloud.
So what can you do? Not much. If you have a computer with a competing AMD processor, pat yourself on the back and breathe easy. Otherwise, make sure that your computer's operating system is up to date with the latest security updates, though fixes for this particular problem may not be widely available for days or even weeks. Intel has yet to publicly comment on the vulnerability, but the consequences will likely reverberate for years.
Highly unlikely.
More like BK, the current CEO tried to ignore it.
The guy is from the Fab and only knows process issues (similar to Craig Barrett)
Not a clue about employees, customers and or quality.
All about the bottom line.
Getting BK fired would be the first good thing that has happened at Intel since he took over.
Corporate servers can’t afford the delay to fix, or the slowness if fixed. Watch them switch to AMD and IBM Power servers quickly. Buy AMD and IBM stock?
Nothing to see. It’s just the NSA opening up your backdoor.
Ping...
Back in the 80’s I had an IBM XT clone that had a ‘Turbo Boost’ button on the front.
I think all it did was turn on a light..................
Pfffttt...this is nothing compared to Apple slowing mobile devices with aging batteries a tiny bit to avoid sudden unexpected system shutdowns then offering nearly free battery replacements on your four year old phone.
Let’s keep some perspective here, people.
My experience with H1Bs is that they don't have any ethic for excellence. Their ethic is based on "good enough" or "slip one by". It is an ethos ingrained in them since childhood.
They take pride in their ability to "get over" and slide through life. Unless someone is looking over their shoulders, you can bet the task with be accomplished will minimal thought and care.
Until I see more info I’m skeptical. This could be nothing more than a timing delay when attempting to access certain kernel memory locations. The fact that there is no demonstrable exploit code makes me think it is just theoretical.
ditto and ditto
Now that it is ‘known’ there will be those who will exploit it................
From the Register article:
It appears, from what AMD software engineer Tom Lendacky was suggesting above, that Intel's CPUs speculatively execute code potentially without performing security checks. It seems it may be possible to craft software in such a way that the processor starts executing an instruction that would normally be blocked such as reading kernel memory from user mode and completes that instruction before the privilege level check occurs.That would allow ring-3-level user code to read ring-0-level kernel data. And that is not good.
Ah
The 0bama chip
It has already been demonstrated that small chunks of Ring 0 memory can be returned to user mode code.
AMD running Linux here, yay
“It has already been demonstrated that small chunks of Ring 0 memory can be returned to user mode code.”
Sure, but can you fetch a bigger, more meaningful chunk of kernel memory? Sure, if you increment the same small thing thousands of times over and over.
I thought you need physical access to the machine to exploit this.
more detailed technical information:
https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/
This is a BFD, WFT, are you kidding me moment.
Software “fix” will slow down every Intel PC by 17%-23%
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.