5 ms·
Apparently, systems with vPRO functionality are also affected, which would include almost all Xeons[1], and many of the upper range consumer chips. If that's t
by kuschku 10y ago
Apparently, systems with vPRO functionality are also affected, which would include almost all Xeons[1], and many of the upper range consumer chips.
If that's the case, this might really become huge.
[1] http://ark.intel.com/Search/FeatureFilter?productType=processors&VProTechnology=true http://ark.intel.com/Search/FeatureFilter?productType=proces...
- jacquesm 10y agoVPro is not in all Xeons, AMT is in only two Xeons that I've been able to find so far, 3400 and E3-1200.
- kuschku 10y agoIntel ARK disagrees with you: http://ark.intel.com/Search/FeatureFilter?productType=processors&VProTechnology=true http://ark.intel.com/Search/FeatureFilter?productType=proces...
- jacquesm 10y agoNo, it does not. Again: VPro is not in all Xeons (though it is in many of them, and it is in most or all of the current product line), AMT is in only very few Xeons. If VPro were in all Xeons then each and every Intel based computer in a DC would be affected. And that's clearly not the case. Also, it is not yet clear - at least to me - whether or not VPro is affected at all but if the ME runs AMT then it definitely is affected.
- kuschku 10y agoEvery Xeon I’ve ever used is in that list, as is every other Intel CPU I’ve ever used. It’s quite an extensive list, and definitely not "only 2"
- jacquesm 10y agoThe 'only 2' are about which Xeons I've found that definitely run AMT. That's something else. Intel isn't helping with their marketing spaghetti, but you're also not helping by suggesting that each and every Xeon is affected. Though if that is the case Intel has a much more serious problem on its hand for suggesting that only business desktops and a couple of low end servers are affected.
- kuschku 10y agoConsidering how right SemiAccurate was already today, I’m inclined to believe him that vPRO and co are affected.
- jacquesm 10y ago> Considering how right SemiAccurate was already today, I’m inclined to believe him that vPRO and co are affected. Well, he was 'SemiAccurate', not accurate so you have all the reason to believe until further notice that VPro is not affected by this bug and claiming different is like shouting 'fire' in a crowded theater. Absent hard proof I don't think you should make such claims. Though I'm sure most sysadmins here would know the difference between a legitimate claim of such magnitude and an inaccurate one. SemiAccurate got the gist right but lots of the details wrong.
- kuschku 10y ago> Well, he was 'SemiAccurate', not accurate so you have all the reason to believe until further notice that VPro is not affected by this bug and claiming different is like shouting 'fire' in a crowded theater. Absent hard proof I don't think you should make such claims. Considering the fact that people claimed a few hours ago AMT would be entirely secure, I think the opposite should hold true right now. Assume everything is vulnerable, unless proven otherwise. This is standard practice in most of IT, but apparently we ignore it here.
- 10y ago
- abeyer 10y agoMore than that: https://ark.intel.com/Search/FeatureFilter?productType=processors&VProTechnology=true https://ark.intel.com/Search/FeatureFilter?productType=proce...
- jacquesm 10y agoThat selects for VPro, which is not the same as AMT. Note that the Intel advisory does not list VPro. If that is the case then tomorrow would be a really good time to buy some AMD stock, there would be very very large numbers of Xeons affected.
- abeyer 10y agoBut the Intel advisory specifically links to this document[1] to assess your exposure, which just says to look for VPro. The info out there is still garbage at this point, but that seems to be the most authoritative I've seen so far. [1] https://communities.intel.com/docs/DOC-5693 https://communities.intel.com/docs/DOC-5693
- jacquesm 10y agoInteresting. So, AMT being a part of VPro might have warranted the inclusion of that term or the term 'Xeon' with a list of SKUs in the original advisory or something if they are affected. Right now it reads as if the server side is a-ok except for some rare beasts, so that's what I'm going on until there is evidence to the contrary. I'm halfway tempted to call my sysadmin out of bed to check one of our systems that I'm quite sure has VPro to see if it is vulnerable. Fortunately my main server is an AMD Bulldozer box. Regardless, if it runs AMT you should check it, VPro or not is really besides the point, it's AMT that is the problem, not VPro as such, which is just another marketing term for the ME and application suite if I understand it correctly, and if that were exploitable instead of 'just' AMT it would be much bigger (and worse) news. But saying that all VPro enabled Xeons or even every Xeon is affected is needlessly alarmist. Here is a wikipedia article on AMT: https://en.wikipedia.org/wiki/Intel_AMT_versions https://en.wikipedia.org/wiki/Intel_AMT_versions If you look at the list of version you can see they all target Desktop and Mobile, no Xeons besides the one I listed earlier. The document you linked also explicitly states 'PC's', not 'servers', though it is definitely possible that some hosting facilities use (cheaper) desktops as servers.