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.
“If this is related to Intel Vpro”
i see nothing in this tech article that says security bug is related to Vpro:
https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/
Tech article states:
“It is understood the bug is present in modern Intel processors produced in the past decade.”
Pinging dayglored for the Windows Ping List. . .
The latest Apple/Mac/iOS Pings can be found by searching Keyword "ApplePingList" on FreeRepublic's Search.
If you want on or off the Mac Ping List, Freepmail me
AMD winning again
If I ran a software company producing browsers or operating systems, I would have death squads hunting these people...
Are you talking about Intel?
My Desktop (HP Pro) is AMD, and those three letters have never looked so good right now!
But my laptops are screwed, though.
Yeah, same at least my main is good
>>If I ran a software company producing browsers or operating systems, I would have death squads hunting these people...
They’re easy to find. Just go to McAfee, Norton, Kaspersky, etc. They know who makes the viruses for them to extort money from us with.
Your experience is the same as my experience. And they hated working for me, because they don’t respect women.The fact that I checked their code and made them redo it if it was slip shod didn’t help. Had to be tough with them.
The new, patched kernel code runs slower on AMD processors as well, because what used to be huge hardware optimizations on any contemporary family of CPUs are entirely bypassed (for example, by constantly flushing caches), to keep privileged information safe. This is why the Linux command du -s now runs only half as fast, even on an AMD processor. The only way to get around this would be to have a different copy of the O/S for Intel and AMD! Might be where things are headed!
Apple uses intel on Macs. But phones and pads dont.
Roflmao! I had one of those too. It was running DOS and it did seem faster.
Youd think that after all these years - theyd know that.
Not a flaw.
It is a feature.
Actually, it sounds more like an NSA-mandated back door than a bug.
Duhh
Computers in China won’t have to have the patch...
Im sure Intel knew about this they just wanted to market those high benchmark speeds so they kept it quiet.
Thanks for the link. Intel’s statement says that the media reports are inaccurate.
The demonstrated exploit could only extract a few bytes, and based on the twitter comments it looks probabilistic and timing sensitive based the behavior of the CPU cache loader. It is plausible that this creates a potential side channel for information leakage, and the fact that the PCID hardware feature (which tags cache lines with a context ID) can allegedly mitigate the problem seems to confirm it that the cache is the source of the information side channel.
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.