Intel responds to security research bug, says no cause for concern

Intel responds to security research bug, says no cause for concern

6 years ago
Anonymous $1bh8zaeyQS

http://www.pcgamer.com/intel-responds-to-security-research-bug-says-no-cause-for-concern/

Late last night, we reported on news that Intel processors have a serious bug that could allow malicious applications to read the contents of protected memory. Today, Intel has officially commented on the situation, but the response is carefully crafted and doesn't provide any significant details of what's going on. Two main points Intel appears to make in its statement are that this isn't a bug—the processors are apparently working as intended—and that there should be no significant performance impact for the 'average computer user.' Let's analyze things a bit more, though.

First, the claim that this is not a bug and that things are working as intended is actually, "recent reports that these exploits are caused by a 'bug' or a 'flaw' and are unique to Intel products are incorrect." Taken as a whole, that doesn't mean much. It could still be a bug or a flaw, but it's not unique to Intel; or it could be that this isn't a bug at all but is simply a new attack vector that wasn't previously considered. Either way, it doesn't mean there aren't potential exploits, but that Intel isn't alone.

Intel responds to security research bug, says no cause for concern

Jan 4, 2018, 12:22am UTC
http://www.pcgamer.com/intel-responds-to-security-research-bug-says-no-cause-for-concern/ >Late last night, we reported on news that Intel processors have a serious bug that could allow malicious applications to read the contents of protected memory. Today, Intel has officially commented on the situation, but the response is carefully crafted and doesn't provide any significant details of what's going on. Two main points Intel appears to make in its statement are that this isn't a bug—the processors are apparently working as intended—and that there should be no significant performance impact for the 'average computer user.' Let's analyze things a bit more, though. >First, the claim that this is not a bug and that things are working as intended is actually, "recent reports that these exploits are caused by a 'bug' or a 'flaw' and are unique to Intel products are incorrect." Taken as a whole, that doesn't mean much. It could still be a bug or a flaw, but it's not unique to Intel; or it could be that this isn't a bug at all but is simply a new attack vector that wasn't previously considered. Either way, it doesn't mean there aren't potential exploits, but that Intel isn't alone.