Intel Responds to Processor Exploit

#5507073

cryohellinc

2018-01-04 09:34

http://straightfromthea.com/wp-content/uploads/2016/04/giphy-4-1.gif

#5507075

sverek

2018-01-04 09:36

I don't like the situation media created. Somebody jumped a gun, published exploits documents too soon and everybody started making wild assumptions without properly grasping a content, creating chaos. AMD jumped a gun and said "We gucci!, suck it Intel!". (I didn't see a single document mentioning testing ZEN CPU) Software vendors are not fully done with releasing patches and probably rushing testing for updates. Really shame to see how fast everyone are pointing fingers and blaming without a proper grasp. Anyway, hopefully there won't be major exploits that take advantage of it.

#5507101

rl66

2018-01-04 10:42

sverek:

I don't like the situation media created. Somebody jumped a gun, published exploits documents too soon and everybody started making wild assumptions without properly grasping a content, creating chaos. AMD jumped a gun and said "We gucci!, suck it Intel!". (I didn't see a single document mentioning testing ZEN CPU) Software vendors are not fully done with releasing patches and probably rushing testing for updates. Really shame to see how fast everyone are pointing fingers and blaming without a proper grasp. Anyway, hopefully there won't be major exploits that take advantage of it.

It wasn't too soon 🙂 ... look wich one have started the fire and what could be the interest of starting too soon 🙂 Both Intel and AMD have responded to minimise... We all know that none system is 100% secured, doing this is poop side marketing.

#5507102

Brutalix

2018-01-04 10:44

sverek:

I don't like the situation media created. Somebody jumped a gun, published exploits documents too soon and everybody started making wild assumptions without properly grasping a content, creating chaos. AMD jumped a gun and said "We gucci!, suck it Intel!". (I didn't see a single document mentioning testing ZEN CPU) Software vendors are not fully done with releasing patches and probably rushing testing for updates. Really shame to see how fast everyone are pointing fingers and blaming without a proper grasp. Anyway, hopefully there won't be major exploits that take advantage of it.

Hm... I am not an AMD fan boy, but I like honest reporting, and this debacle started in the linux kernel org. after intel engineers applied an kernel patch that hampered all CPU's due to the security flaw in the intel cpu's. The AMD processors doesn't allow the same speculative references, that accesses higher priviliged data (ring 0) from a lesser (ring 3) mode. AMD issued a patch in december to fix the problem the intel created for their prosessors, this patch was ignored for some time, till some kernel programmers started shouting foul that the intel patch was used and including all AMD cpus as well, and not including the AMD patch. This ended when Linus included the AMD patch. AMD also released a statement with a nice summary for the flaws/risks issued by google.

Google Project Zero (GPZ) Research Title Details Variant One Bounds Check Bypass: Resolved by software / OS updates to be made available by system vendors and manufacturers. Negligible performance impact expected. Variant Two Branch Target Injection: Differences in AMD architecture mean there is a near zero risk of exploitation of this variant. Vulnerability to Variant 2 has not been demonstrated on AMD processors to date. Variant Three Rogue Data Cache Load: Zero AMD vulnerability due to AMD architecture differences.(MELTDOWN BUG)

Kind regards. B.

#5507113

Alessio1989

2018-01-04 11:27

So far only with Intel CPU you can get kernel memory reference. Metldown still requires an ad hoc OS kernel solution since it cannot be patched via microcode, with performance impact on every every context switch. Intel space shuttle is burning buy they are complaining about wrong curtains colours of AMD and ARM. Bound checking could be easily patched by the OS on every executable loading. Not sure about branch target.

#5507127

RealNC

2018-01-04 11:52

This statement looks like it's meant for the stock market, not for IT people.

#5507193

__hollywood|meo

2018-01-04 15:03

RealNC:

This statement looks like it's meant for the stock market, not for IT people.

nail on the head. they released this so that their stock would stop tanking, & it did. its smoke & mirrors for their investors who cant distinguish between the broad applicability of meltdowns quite frankly catastrophic security ramifications...& spectres laughable risk by comparison. they were quite careful to ensure that this press release was worded in a misleading way, banking on the ignorance of the general public. pisses me off to no end. "intel believes it has the most secure processors in the world"..................................... ::edited because how2spell::

#5507194

fry178

2018-01-04 15:06

@cryohellinc +1 OT: cant wait for next season..

#5507199

WhiteLightning

Moderator

2018-01-04 15:14

windows 10 patches https://www.catalog.update.microsoft.com/Search.aspx?q=KB4056892

#5507213

D3M1G0D

2018-01-04 15:51

__hollywood|meo:

nail on the head. they released this so that their stock would stop tanking, & it did. its smoke & mirrors for their investors who cant distinguish between the broad applicability of meltdowns quite frankly catastrophic security ramifications...& spectres laughable risk by comparison. they were quite careful to ensure that this press release was worded in a misleading way, banking on the ignorance of the general public. pisses me off to no end.

Well, if that was the reason then it failed. Intel stock is still tanking (and AMD stock is still rocketing). Investors may not be the brightest bulbs in the room, but I think they got the message that Intel CPUs have a unique vulnerability to meltdown.

#5507215

__hollywood|meo

2018-01-04 16:02

yikes, youre right. intel had settled at 44 yesterday iirc, but on market open today: its dropping again. ill be honest, im getting a little sadistic pleasure out of that

#5507227

Turanis

2018-01-04 16:31

Indeed,after 2017 Intel cpu bugs ,now again in the begining of 2018 they have another(s) bug. Its bad for business and bad for inverstors.

#5507274

sykozis

2018-01-04 18:12

I don't recall any major CPU bugs for Intel in 2017. There has been an issue of Intel's "Management Engine" for more than a year. Until recently, Intel had been denying that their "management engine" could pose security risks. Only recently did Intel actually acknowledge that fact.