Intel Lied To Industry on Security Vulnerabilities

SHARE THIS NEWS ON SOCIAL MEDIA: Share

INTEL LIES ABOUT BACKDOOR.png

 

Intel Lied To Industry on Security Vulnerabilities

by Paul Thurrott in Hardware with 33 Comments

- Intel says "no exploits have been documented", yet many sites HAVE posted step-by-step exploit instructions

- Google and Facebook targeted by hackers with goal of acquiring their corporate records and political rigging data

Caught in the center of a security vulnerability storm, Intel has done the unthinkable and understated the severity of the problems.

Yes, there is a lot of blame to go around here.

It was wrong for The Register (no link, deliberate) to publish information about these CPU flaws before the industry could issue all of the fixes it was readying, for example.

And it was dumb of AMD to brag—literally—that it saw almost no impact from these flaws in its own chipsets.

But if I were to point the finger of blame at one company here, and I will, it would have to be Intel. The microprocessor giant has behaved in an irresponsible manner that is just hard to explain.

Consider just three of the quotes from the microprocessor’s statement, which I reported on yesterday. Each of these claims is technically true to some degree. But oh so wrong in all the ways that are important.

“Intel believes these exploits do not have the potential to corrupt, modify or delete data.”

Intel probably does believe that. But the firm left out the most important bit: Exploits based on the revealed flaws have the ability to steal your data. And this can happen in cloud-based servers, which makes the flaws particularly dangerous.

“Recent reports that these exploits are caused by a ‘bug’ or a ‘flaw’ and are unique to Intel products are incorrect.”

It’s unclear why Intel put quotes around the words “bug” and “flaw” since there are in fact two bugs—or flaws—in all of its microprocessors. Are they unique to Intel chips? No. But Intel is hit the hardest here, because it has the most affected microprocessors still in use in the market, in particular in server and cloud workloads. And there is no fix for one of the flaws.

“Contrary to some reports, any performance impacts are workload-dependent, and, for the average computer user, should not be significant and will be mitigated over time.”

Put simply, the fixes that are required will impact the performance of the CPU and thus the system of which it is part. And there is an evolving understanding of what this impact will be across those workloads, yes. So while it is probably fair to say that the performance impact on end-user PCs will be “not significant,” this comment neatly leaves out the most important bit. The performance impact to Linux-based servers—which power about 30 percent of the Internet—could be as high as 30 percent.

Put simply, each of these statements is irresponsible. And Intel needs to be held accountable for this misinformation.

 

 

  • Intel has a massive fuck up only effecting them (Meltdown) that allows people to use predictive memory in their processors to view protected info and is very easily executed. It was patched but because protected files can't be accessed the normal way, it caused a 30% hit to performance. This was patched via firmware but they're still open to Spectre.

  • Spectre is a flaw that is similar. This is what effects AMD/ARM as well as Patched Intel. The flaw is again unproctected processes can access protected processes using the processor architecture. It is hard to execute and there is no patch in sight because it is exploiting the way the processor runs, not a "back door" or "bug"

  • Apparently processors use statistical prediction patterns to bring information quicker, sometimes that means protected info or memory logs with protected info (I'm not a Computer Science III 1337 hax0r, so forgive me if this is too dumb dumb an explaination).

  • Intel fucked up by having a "bug" (but in reality most likely a NSA/Mossad/CIA back door) that made Spectre so easy even a script kiddie can do it.

  • Chances you are definitely effected, your personal PC/Smart Phone/consoles/etc. are fine. Anyone with the knowledge to run this is most likely gonna go after big game first.

  • The Big game targets (Google, Amazon, Credit Card Companies, Gov websites, etc.) however are not and this is what will fuck people.

  • The spin your seeing right now is blame it all on intel and install the patch that makes your computer slower and you'll be A-Okay. In reality, we should be shitting bricks over how shitty most websites have been running their security and best case scenerio is a shit load of SSL keys just got released in the wild. Worse case is in theory anyone with the resources can build their own NSA.

  • Intel knew about this since June 2016

 

We translated Intel's crap attempt to spin its way out of CPU security bug PR nightmare

As Linus Torvalds lets rip on Chipzilla

By Thomas Claburn in San Francisco 4 Jan 2018 at 02:46

210 Reg comments SHARE ▼

Analysis In the wake of The Register's report on Tuesday about the vulnerabilities affecting Intel chips, Chipzilla on Wednesday issued a press release to address the problems disclosed by Google's security researchers that afternoon.

To help put Intel's claims into context, we've annotated the text. Bold is Intel's spin.

Intel and other technology companies have been made aware of new security research describing software analysis methods that, when used for malicious purposes, have the potential to improperly gather sensitive data from computing devices that are operating as designed.

Translation: When malware steals your stuff, your Intel chip is working as designed. Also, this is why our stock price fell. Please make other stock prices fall, thank you.

By the way, here's what Linux kernel supremo Linus Torvalds had to sayabout this: "I think somebody inside of Intel needs to really take a long hard look at their CPUs, and actually admit that they have issues instead of writing PR blurbs that say that everything works as designed.

"Is Intel basically saying 'we are committed to selling you shit forever and ever, and never fixing anything'?"

What Intel described as "software analysis methods," security researchers describe thus: "Meltdown breaks all security assumptions given by the CPU’s memory isolation capabilities."

"Meltdown" is the name given to a side-channel attack on memory isolation that affects most Intel chips since 2010, as well as a few Arm cores. Intel's chips may be "operating as designed" but it is this processor design that's the issue; based on the research that has been published, the current design is inadequate and insecure.

Meltdown – on Intel CPUs and the Arm Cortex-A75 – allows normal applications to read protected kernel memory, allowing them to steal passwords and other secrets. It is easy to exploit, but easy to patch – and workarounds to kill the vulnerability are available for Windows and Linux, and are already in macOS High Sierra, for Intel parts. There are Linux kernel patches available for the Cortex-A75, which isn't even available yet.

There's also another security flaw named Spectre that affects, to varying degrees, Intel, AMD, and Arm. Depending on your CPU, Spectre allows normal apps to potentially steal information from other apps, the kernel, or the underlying hypervisor. Spectre is difficult to exploit, but also difficult to fully patch – and is going to be the real stinger from all of this.

You can find a summary of the Meltdown and Spectre bugs, here.

Intel believes these exploits do not have the potential to corrupt, modify or delete data.

Translation: Look, over here! Scary words! And we deny them! And you'll forget that this is about stealing information, not tampering with it.

Funnily enough, no one said the security flaws could be used to directly alter data. Instead of talking about what these exploits don't do, let's focus on what they make possible.

On vulnerable systems, Meltdown allows user programs to read from private and sensitive kernel address spaces, including kernel-sharing sandboxes like Docker or Xen in paravirtualization mode. And when you've stolen the keys to the kingdom, such as cryptographic secrets, you'll probably find you can indeed corrupt, modify or delete data, pal.

Recent reports that these exploits are caused by a “bug” or a “flaw” and are unique to Intel products are incorrect.

Translation: Pleeeeeease, pleeeeease do not sue us for shipping faulty products or make us recall millions of chips.

Bug. Flaw. Security shortcoming. Design oversight. Blueprint blunder. Bungled architecture. It's the same difference. Security researchers, describing Meltdown, said: "On the microarchitectural level (e.g., the actual hardware implementation), there is an exploitable security problem."

The exploits described this week against processors rely on unsafe system designs. Flawed system designs, if you will. Buggy system designs.

Based on the analysis to date, many types of computing devices — with many different vendors’ processors and operating systems — are susceptible to these exploits.

Translation: We weren't the only one. And if we're going down, we're taking every last one of you with us.

Chipzilla doesn't want you to know that every Intel processor since 1995 that implements out-of-order execution is potentially affected by Meltdown – except Itanium, and the Atom before 2013.

Intel is committed to product and customer security and is working closely with many other technology companies, including AMD, ARM Holdings and several operating system vendors, to develop an industry-wide approach to resolve this issue promptly and constructively. Intel has begun providing software and firmware updates to mitigate these exploits. Contrary to some reports, any performance impacts are workload-dependent, and, for the average computer user, should not be significant and will be mitigated over time.

Translation: Just fucking leave us alone.

While Intel may be working with AMD, Arm, and other system vendors, any performance hit incurred from patching Meltdown is not an issue for these vendors. AMD isn't affected by the bug, and only the Arm Cortex-A75 is susceptible to the vulnerability.

The performance hit is due to implementing Kernel Page Table Isolation, or KPTI (previously called KAISER) to close the security hole. This pushes the kernel into a separate address space so it cannot be accessed at all by the running processes. The downside is that whenever an application needs the kernel to do something useful, such as read a file or send some network traffic, the CPU has to switch over to the kernel's virtual address space. This takes time, and doing it a lot will slow down the machine.

The KPTI overhead for the Cortex-A75 isn't known at the moment, and is estimated to be minimal. Arm may even rejig the A75 in light of these discoveries. As for Intel systems, we stated in our original report:

The effects are still being benchmarked, however we're looking at a ballpark figure of five to 30 per cent slow down, depending on the task and the processor model. More recent Intel chips have features – such as PCID – to reduce the performance hit. Your mileage may vary.

These figures were based on estimates from people working on the KPTI patches, and from simple benchmarks, such as asking a PostgreSQL database to select all records in a data store, and adding up all file sizes of documents on a disk. Some people have already reported noticeable degraded performance from their cloud-hosted virtual machines after applying the Meltdown patches. Some cloud vendors insist there won't be a problem.

It really boils down to – as we said, and Intel pointed out – your workload. If you just play games on your PC, you will not see a slowdown, beyond any delays caused by file loading, because the software rarely jumps to the kernel during gameplay. Your game will be mostly talking to the graphics processor.

If all you do is browse Twitter, write emails, and type away in a word processor, you probably won't notice any difference. If you do a lot of in-memory number crunching, you won't see much of an impact because again the kernel isn't getting in the way. If you have PCID support enabled on your hardware and in your kernel, any performance hit should be minimized.

If you hammer the disk, the network, or use software that makes lots of system calls in and out of the kernel, and you're lacking working PCID support, you will see a performance hit. And it's a good idea to warn you, right?

It's a given for this particular issue that any slowdown is dependent upon the kind of work the affected system is being asked to do. Gamers will maintain their frame rates, but that's not what this is about. It's about enterprise workloads and data centers. With reports of SQL database slowdowns of up to 20 or so per cent, it seems premature to say the impact should not be significant. If a company's AWS, Microsoft Azure, or Google Cloud bill ends up being, say, three, five or eight per cent higher as a consequence of prolonged compute times, that's significant.

No doubt the patches will be benchmarked, and we'll write about them.

Intel is committed to the industry best practice of responsible disclosure of potential security issues, which is why Intel and other vendors had planned to disclose this issue next week when more software and firmware updates will be available. However, Intel is making this statement today because of the current inaccurate media reports.

Translation: We were gonna say something next week, but those bastards at The Register blew the lid on it early so, uh, so, fake news! Fake news! NO PUPPET!

The preferred phrase at present is "coordinated disclosure." "Responsible disclosure" suggests the media and security researchers have been irresponsible for reporting on this issue before Intel was ready to go public. Once we get into assigning blame, that invites terms like "responsible microarchitecture design" or "responsible sales of processors known to contain vulnerabilities" or "responsible handling of security disclosures made last June."

Also, it's not clear which media reports are inaccurate, since Intel is not addressing anyone specifically.

Check with your operating system vendor or system manufacturer and apply any available updates as soon as they are available. Following good security practices that protect against malware in general will also help protect against possible exploitation until updates can be applied.

Translation: Don't click on any bad links or emails, you rubes.

Thanks for that. And remember to lock your doors at night.

Intel believes its products are the most secure in the world and that, with the support of its partners, the current solutions to this issue provide the best possible security for its customers.

Translation: Who else are you gonna buy this stuff from?

One step below security by obscurity, there's security by belief. Demand more. ®

Intel Released "Coffee Lake" Knowing it Was Vulnerable to Spectre and Meltdown

Intel Released "Coffee Lake" Knowing it Was Vulnerable to Spectre and Meltdown (techpowerup.com)

submitted  ago by Troll to technology (+56|-0)

 

Remember the Equifax data breach? All of the executives who dumped their stock after learning of the breach got off scot free

Remember the Equifax data breach? All of the executives who dumped their stock after learning of the breach got off scot free (cnbc.com)

submitted  ago by Saufsoldat to technology (+174|-0)

Linus Torvalds Latest Meltdown: 'Is Intel Selling Shit And Never Willing To Fix Anything?'

Linus Torvalds Latest Meltdown: 'Is Intel Selling Shit And Never Willing To Fix Anything?' (fossbytes.com)

submitted  ago by fluxusp to technology (+35|-0)

 

Intel CEO Says They Don't Owe You Shit: Absolutely no Intel chip recall or free PCs will be coming.

Intel CEO Says They Don't Owe You Shit: Absolutely no Intel chip recall or free PCs will be coming. (cnet.com)

submitted  ago by tendiesonfloor to news (+67|-1)

Anal Cancer: The New Gay Epidemic the Media Won't Talk About - If AIDs Doesn't Get You, The Anal Cancer Will...

Anal Cancer: Intel's New Gay Epidemic the Media Won't Talk About - If AIDs Doesn't Get You, The Intel Anal Cancer Will... (pjmedia.com)

submitted  ago by Scrooblemeyer to news (+96|-1)

New Intel Logo

New Intel Logo (i.imgjar.co)

submitted  ago by Troll to technology (+171|-1)

Report: Intel CEO Sold $24 Million in Stock While Company Was Aware of Massive CPU Bug - Breitbart

Report: Intel CEO Sold $24 Million in Stock While Company Was Aware of Massive CPU Bug - Breitbart (breitbart.com)

submitted  ago by Bad-R0nald to technology (+93|-2)

 

Meltdown, Spectre: The password theft bugs at the heart of Intel CPUs(theregister.co.uk)

submitted  ago by lbruiser to technology (+22|-0)

 

=======

 

 

SHARE THIS NEWS ON SOCIAL MEDIA: Share

They posted on the same topic

Trackback URL : https://congressionalreview.net/index.php?trackback/154

This post's comments feed

Aperçu de site