News for hackers. Stuff that matters.
Re:Reading privileged memory with a side-channel by cesarb on Wednesday January 03, 2018 @06:06PM (#16066314)
You know it's a bad one when Project Zero allows more than its usual 90-day deadline...
Re:Reading privileged memory with a side-channel by blattimwind on Wednesday January 03, 2018 @06:19PM (#16066428)
"Which systems are affected?" – "All systems." – "Come again?"
Re:Reading privileged memory with a side-channel by Ajedi32 on Wednesday January 03, 2018 @07:47PM (#16066966)
From the FAQ on spectreattack.com:

> Q: Am I affected by the bug?

> A: Most certainly, yes.

Scary.

Re:Reading privileged memory with a side-channel by Symmetry on Wednesday January 03, 2018 @08:00PM (#16067060)
If you're using an in order processor, a Nexus 9 tablet say, then you should be safe.
Re:Reading privileged memory with a side-channel by Symmetry on Thursday January 04, 2018 @07:36AM (#16069860)
I wasn't thinking straight last night. Basically all in order application processors use speculative execution.
Re:Reading privileged memory with a side-channel by blattimwind on Thursday January 04, 2018 @07:43AM (#16069904)
Even a low-power core like a Cortex-M7 can do some speculative execution through its branch predictor.

Though of course a M7 isn't running VMs, and probably isn't running any kind of attacker-controlled code (scripting included - its there, but rare), so many of the vectors aren't present.

Re:Reading privileged memory with a side-channel by jsmthrowaway on Wednesday January 03, 2018 @06:33PM (#16066534)
Then front-runs the negotiated timeline anyway, catching projects like Xen off guard (it seems like)[0]. Will be interested to read the postmortem of the entire process from start to finish, and Xen is promising one from their perspective. I'd be especially interested to understand whether public intel was concrete enough to rush this out the door, because it didn't seem like it was, but I probably missed something.

[0]: https://xenbits.xen.org/xsa/advisory-254.html

Re:Reading privileged memory with a side-channel by londons_explore on Wednesday January 03, 2018 @09:18PM (#16067456)
I reimplemented variant 3 based solely on clues from twitter posts yesterday.

I am by no means a computer security guru - I just did a CPU architecture course at uni and figured I'd cowboy up an implementation. It worked nearly first time, and can read both kernel and userspace pages from userspace by fooling the branch predictor into going down the wrong path, and relying on the permission checks to be slower than the data reads from a virtually addressed cache. It can only access stuff already cached though, so you can't do a full memory dump with it.

Re:Reading privileged memory with a side-channel by baq on Wednesday January 03, 2018 @06:48PM (#16066639)
speculation was apparently hitting very close to home allowing attackers with resources (think nation states) to start developing their own tooling. at least this early announcement allows people with sensitive data to quickly move to dedicated instances.

edit: well it didn't take a nation state after all: https://twitter.com/brainsmoke/status/948561799875502080 - given that, you can be sure that everybody who counts is frantically launching these on your clouds gathering whatever they can.