# Intel dun goofed

**URL:** <https://tw.forumosa.com/t/intel-dun-goofed/166186>\
**Category:** Technology\
**Created:** [January 3, 2018, 8:26am UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186 "2018-01-03T08:26:07Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![IbisWtf](https://forumosa-12829.kxcdn.com/user_avatar/tw.forumosa.com/ibiswtf/32/67943_2.png) [@IbisWtf](https://tw.forumosa.com/u/IbisWtf)\
**Post date:** [January 3, 2018, 8:26am UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186/1 "2018-01-03T08:26:07Z")

</div>

[https://www.dangerous.com/39808/intel-cpus-major-security-flaw-fixing-causes-huge-performance-hit/](https://www.dangerous.com/39808/intel-cpus-major-security-flaw-fixing-causes-huge-performance-hit/)

“It’s impossible to fix with a chip-based update, and requires a software-based solution through the operating system, which in turn causes a performance hit of up to 30 percent.”

It’s being reported by all tech websites.

![amdlol](https://forumosa-12829.kxcdn.com/images/transparent.png)

---

<div class="post-metadata">

**Author:** ![hansioux](https://forumosa-12829.kxcdn.com/user_avatar/tw.forumosa.com/hansioux/32/253648_2.png) [@hansioux](https://tw.forumosa.com/u/hansioux)\
**Post date:** [January 3, 2018, 9:24am UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186/2 "2018-01-03T09:24:27Z")

</div>

That’s in addition to their Intel-SA-00086 Management Engine vulnerability…

---

<div class="post-metadata">

**Author:** ![mad\_masala](https://forumosa-12829.kxcdn.com/user_avatar/tw.forumosa.com/mad_masala/32/182103_2.png) [@mad\_masala](https://tw.forumosa.com/u/mad_masala)\
**Post date:** [January 3, 2018, 10:39am UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186/3 "2018-01-03T10:39:09Z")

</div>

I misunderstood it, I thought that fixing it the CPU would increase the performance by a 30%!

---

<div class="post-metadata">

**Author:** ![IbisWtf](https://forumosa-12829.kxcdn.com/user_avatar/tw.forumosa.com/ibiswtf/32/67943_2.png) [@IbisWtf](https://tw.forumosa.com/u/IbisWtf)\
**Post date:** [January 3, 2018, 12:13pm UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186/4 "2018-01-03T12:13:14Z")

</div>

That would have been neat!

---

<div class="post-metadata">

**Author:** ![tempogain](https://forumosa-12829.kxcdn.com/user_avatar/tw.forumosa.com/tempogain/32/264650_2.png) [@tempogain](https://tw.forumosa.com/u/tempogain)\
**Post date:** [January 3, 2018, 12:44pm UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186/5 "2018-01-03T12:44:45Z")

</div>

That seems fairly annoying. I think I’m Intel

---

<div class="post-metadata">

**Author:** ![viator\_de](https://forumosa-12829.kxcdn.com/user_avatar/tw.forumosa.com/viator_de/32/176557_2.png) [@viator\_de](https://tw.forumosa.com/u/viator_de)\
**Post date:** [January 4, 2018, 1:19am UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186/6 "2018-01-04T01:19:34Z")

</div>

This is a big problem. You can access kernel memory with an unprivileged process and nothing can stop it and it leaves no traces. Sandboxing in virtual machines does not stop it (cloud providers).  
It was supposed to be disclosed next week but rumors and panic made them publish it early.

* * *

**Meltdown and Spectre**  
Bugs in modern computers leak passwords and sensitive data.

> **[Reading privileged memory with a side-channel](https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html)**
>
> Posted by Jann Horn, Project Zero We have discovered that CPU data cache timing can be abused to efficiently leak information out of mi...

[https://meltdownattack.com](https://meltdownattack.com)

* * *

There are three variants and the most serious one only affects Intel (Meltdown), but other variants also affect AMD, ARM, etc.

Spectre (variants 1 and 2)  
Meltdown (variant 3) affects almost all Intel-CPUs since 1995

Variant 1: bounds check bypass (CVE-2017-5753)  
Variant 2: branch target injection (CVE-2017-5715)  
Variant 3: rogue data cache load (CVE-2017-5754)

---

<div class="post-metadata">

**Author:** ![finley](https://forumosa-12829.kxcdn.com/letter_avatar_proxy/v4/letter/f/57b2e6/32.png) [@finley](https://tw.forumosa.com/u/finley)\
**Post date:** [January 4, 2018, 1:31am UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186/7 "2018-01-04T01:31:47Z")

</div>

> [@viator\_de](#):
>
> This is a big problem.

That stuff makes my head hurt. Although I can see roughly what they’re getting at (considering I haven’t had my coffee yet) I’m not sure this follows:

> [@](#):
>
> Bugs in modern computers leak passwords and sensitive data.

It would be literally like looking for a needle in a haystack. Now I realise that’s precisely what computers are good at, but I suspect a virus scavenging leftover scraps from the cache would consume so much CPU time that people would notice something badly wrong and do a virus scan.

Or perhaps I overestimate people’s competence with computers.

---

<div class="post-metadata">

**Author:** ![viator\_de](https://forumosa-12829.kxcdn.com/user_avatar/tw.forumosa.com/viator_de/32/176557_2.png) [@viator\_de](https://tw.forumosa.com/u/viator_de)\
**Post date:** [January 4, 2018, 1:50am UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186/8 "2018-01-04T01:50:26Z")

</div>

A key-logger that does not need to hook the system, can be started in a silent unprivileged process and is therefore undetectable by antivirus. AVs can detect it after the AV companies get a sample of the key-logger code and make a hash signature. But small changes make it invisible to AV again.

But who would go after individuals if there are other juicy targets. Run the exploit on the cloud. The resources are shared and you will find access keys to other cloud accounts that happen to run code on the same hardware. Get access to huge databases of companies that use cloud services.

It is a big deal as it compromises security everywhere until the systems have been patched.

---

<div class="post-metadata">

**Author:** ![The\_Seeker](https://forumosa-12829.kxcdn.com/letter_avatar_proxy/v4/letter/t/cc9497/32.png) [@The\_Seeker](https://tw.forumosa.com/u/The_Seeker)\
**Post date:** [January 4, 2018, 3:27am UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186/9 "2018-01-04T03:27:53Z")

</div>

If the CPU has a design flaw, would it be possible to order a recall for newer purchases and perhaps a significant discount for people to upgrade to a newer model. how far back was this problem?

---

<div class="post-metadata">

**Author:** ![viator\_de](https://forumosa-12829.kxcdn.com/user_avatar/tw.forumosa.com/viator_de/32/176557_2.png) [@viator\_de](https://tw.forumosa.com/u/viator_de)\
**Post date:** [January 4, 2018, 5:34am UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186/10 "2018-01-04T05:34:24Z")

</div>

> [@The\_Seeker](#):
>
> how far back was this problem?

> [@viator\_de](#):
>
> Meltdown (variant 3) affects almost all Intel-CPUs since 1995

The meltdown flaw can be fixed with software patches. Windows, MacOS and Linux already have patches made. This results in slightly lower performance. For end users the slowdown is almost non existent. The slowdowns can be big for some databases (cloud).

So big datacenters using Intel might get some reparatons from Intel as they have the resources to preassure Intel.

Btw.[Intel CEO sold $24 million in company stock recently](http://www.businessinsider.com/intel-ceo-krzanich-sold-shares-after-company-was-informed-of-chip-flaw-2018-1) (everything he was legally able to sell).

---

<div class="post-metadata">

**Author:** ![tempogain](https://forumosa-12829.kxcdn.com/user_avatar/tw.forumosa.com/tempogain/32/264650_2.png) [@tempogain](https://tw.forumosa.com/u/tempogain)\
**Post date:** [January 4, 2018, 5:41am UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186/11 "2018-01-04T05:41:10Z")

</div>

Doing my updates now. We’ll see what happens

---

<div class="post-metadata">

**Author:** ![tempogain](https://forumosa-12829.kxcdn.com/user_avatar/tw.forumosa.com/tempogain/32/264650_2.png) [@tempogain](https://tw.forumosa.com/u/tempogain)\
**Post date:** [January 4, 2018, 6:28am UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186/12 "2018-01-04T06:28:54Z")

</div>

Don’t think that update is out yet actually

---

<div class="post-metadata">

**Author:** ![viator\_de](https://forumosa-12829.kxcdn.com/user_avatar/tw.forumosa.com/viator_de/32/176557_2.png) [@viator\_de](https://tw.forumosa.com/u/viator_de)\
**Post date:** [January 4, 2018, 8:01am UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186/13 "2018-01-04T08:01:20Z")

</div>

Meltdown fixed in

macOS 10.13.2  
Windows 10 Insider Preview Build 17063 (public patch next Tuesday)  
Linux-Kernel 4.14.11

---

<div class="post-metadata">

**Author:** ![viator\_de](https://forumosa-12829.kxcdn.com/user_avatar/tw.forumosa.com/viator_de/32/176557_2.png) [@viator\_de](https://tw.forumosa.com/u/viator_de)\
**Post date:** [January 5, 2018, 12:11am UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186/14 "2018-01-05T00:11:20Z")

</div>

> [@viator\_de](#):
>
> A key-logger that does not need to hook the system

Done…

[https://twitter.com/misc0110/status/948706387491786752](https://twitter.com/misc0110/status/948706387491786752)

---

<div class="post-metadata">

**Author:** ![IbisWtf](https://forumosa-12829.kxcdn.com/user_avatar/tw.forumosa.com/ibiswtf/32/67943_2.png) [@IbisWtf](https://tw.forumosa.com/u/IbisWtf)\
**Post date:** [January 5, 2018, 2:27am UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186/15 "2018-01-05T02:27:37Z")

</div>

Amd stock up 5% from yesterday, Intel down 2%.

---

<div class="post-metadata">

**Author:** ![tempogain](https://forumosa-12829.kxcdn.com/user_avatar/tw.forumosa.com/tempogain/32/264650_2.png) [@tempogain](https://tw.forumosa.com/u/tempogain)\
**Post date:** [January 14, 2018, 12:35pm UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186/16 "2018-01-14T12:35:19Z")

</div>

Installing the latest Linux kernel now. Let’s see…

---

<div class="post-metadata">

**Author:** ![tempogain](https://forumosa-12829.kxcdn.com/user_avatar/tw.forumosa.com/tempogain/32/264650_2.png) [@tempogain](https://tw.forumosa.com/u/tempogain)\
**Post date:** [January 15, 2018, 10:09am UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186/17 "2018-01-15T10:09:47Z")

</div>

UP to latest kernel and all seems well, but my main game isn’t working in background mode after some recent update which basically makes it unplayable.

---

<div class="post-metadata">

**Author:** ![IbisWtf](https://forumosa-12829.kxcdn.com/user_avatar/tw.forumosa.com/ibiswtf/32/67943_2.png) [@IbisWtf](https://tw.forumosa.com/u/IbisWtf)\
**Post date:** [January 23, 2018, 6:00am UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186/18 "2018-01-23T06:00:04Z")

</div>

LIinux’ boss said the patches are garbage and Intel is fooking insane, lol

---

<div class="post-metadata">

**Author:** ![hansioux](https://forumosa-12829.kxcdn.com/user_avatar/tw.forumosa.com/hansioux/32/253648_2.png) [@hansioux](https://tw.forumosa.com/u/hansioux)\
**Post date:** [January 23, 2018, 7:29am UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186/19 "2018-01-23T07:29:55Z")

</div>

> [@IbisWtf](#):
>
> LIinux’ boss said the patches are garbage and Intel is fooking insane, lol

Linus loves himself the f-word.

---

<div class="post-metadata">

**Author:** ![viator\_de](https://forumosa-12829.kxcdn.com/user_avatar/tw.forumosa.com/viator_de/32/176557_2.png) [@viator\_de](https://tw.forumosa.com/u/viator_de)\
**Post date:** [January 23, 2018, 1:19pm UTC](https://tw.forumosa.com/t/intel-dun-goofed/166186/20 "2018-01-23T13:19:35Z")

</div>

> [@Linus Torvalds – Jan 21 2018](#):
>
> **The whole hardware interface is literally mis-designed by morons.**

[http://lkml.iu.edu/hypermail/linux/kernel/1801.2/04628.html](http://lkml.iu.edu/hypermail/linux/kernel/1801.2/04628.html)

😂

[Next page](https://tw.forumosa.com/t/intel-dun-goofed/166186.md?page=2)
