Security Researchers Publish Ryzen Flaws, Gave AMD 24 Hours Prior Notice

Re:Security Researchers Publish Ryzen Flaws, Gave AMD 24 Hou... by therein on Tuesday March 13, 2018 @08:06PM (#16581074)

> Enable `#shared-array-buffer` in `chrome:///flags` under your own risk...

[ Parent | on HN ]

Re:Security Researchers Publish Ryzen Flaws, Gave AMD 24 Hou... by tptacek on Tuesday March 13, 2018 @08:09PM (#16581092)

SharedArrayBuffer was disabled exactly because vulnerabilities like this are easily exploitable (but there are POCs that don't depend on it).

[ Parent | on HN ]

Re:Security Researchers Publish Ryzen Flaws, Gave AMD 24 Hou... by ComputerGuru on Tuesday March 13, 2018 @08:57PM (#16581372)

It was only disabled as a mitigation to these specific attacks, in case you though it was an experimental or “at your own risk” type of thing.

[ Parent | on HN ]

Re:Security Researchers Publish Ryzen Flaws, Gave AMD 24 Hou... by daira on Wednesday March 14, 2018 @04:09AM (#16583126)

Disabling SharedArrayBuffer is just stopping the most obvious method of exploitation; it's by no means a fix. Expect a slew of papers over the next few years on other methods of exploitation from JS.

[ Parent | on HN ]

Re:Security Researchers Publish Ryzen Flaws, Gave AMD 24 Hou... by mtgx on Tuesday March 13, 2018 @08:28PM (#16581193)

Every single browser had to disable that feature because of those flaws.

[ Parent | on HN ]