21–30 of 349 posts
From FAQ: [Q] How long have users been exposed to this vulnerability? [A] At least nine years. The affected processors have been around since 2014. Amazing how these vulnerabilities sit around unnoticed for years and then it takes two weeks for someone to code up an exploit.
> [A] Other processors have shared SRAM memory inside the core, such as hardware register files and fill buffers. Manufacturers must design shared memory units with extra care to prevent data from leaking across different security domains and invest more in security validation and testing.
Not sure what to make of this wording. Thinly veiled threat? Hint that other embargoes are in place?
Stop. Releasing. Attack research. Without. Detection strategies.
Also many attacks are not really feasible to detect if it's happened - that's like trying to know if the mailman read your postcard.
You can develop executable scanning techniques, but people are a lot more concerned about preventing it in the first place than catching it in the act. Why would you leave people vulnerable so they can watch data get stolen - instead of just fixing the issue?
Stop. Releasing. Attack research. Without. Detection strategies.
I'm getting annoyed with all of these yawning security holes in Intel's CPUs. I'm tempted to replace my Intel MacBook Pro with an Apple Silicon model sooner than I normally would.
Earlier quoted context omitted.
If I'm reading this right, the caveat is that the exploit only lets you read registers that have been saved for context-switching. So, in order to extract data, that data must be in constant active use (i.e. loaded in a register) at the time of the attack.
Would environmental variables be something that shows up in context-switching?
> [Q] Should other processor vendors and designers be concerned? > [A] Other processors have shared SRAM memory inside the core, such as hardware register files and fill buffers. Manufacturers must design shared memory units with extra care to prevent data from leaking across different security domains and invest more in security validation and testing. Not sure what to make of this wording. Thinly veiled threat? Hin…
Stop. Releasing. Attack research. Without. Detection strategies.