Security engineer, CTF player for @0rganizers. Mastodon: @nspace@infosec.exchange

Joined January 2018
Filter
Exclude
Time range
-
Near
EntrySign won 2 pwnies 🤯🤯
1
1
30
Our new blog post is out! Check it out, I think we got some really cool results in this one.
Our latest post details how we exploited Retbleed (a CPU vulnerability) to compromise a machine from a sandboxed process and VM! Curious? 👇 bughunters.google.com/blog/6…
1
3
30
Very cool! Yeah let's get in touch.
1
EntrySign was nominated for two Pwnies (best crypto bug and best desktop bug)! 🥳 piped.video/live/TuKPA-CeDFA… @__spq__ @sirdarckcat @taviso
6
1
42
The recording of our OffensiveCon presentation about EntrySign is live! piped.video/sUFDKTaCQEk Slides at entrysign.top @sirdarckcat @__spq__
2
21
3
101
As promised, more details! TL;DR: AMD used CMAC with an example key from the standard as a hash function for the microcode update signatures. This let us create signatures that look valid to the CPU.
Here are the details about the AMD Signature verification vulnerability we worked on, Enjoy! bughunters.google.com/blog/5…
1
6
51
Replying to @yo_yo_yo_jbo
No, it's a kernel mode virtual address, so it's 0xffffXXXXYYYYZZZZ but on 64-bit Linux unsigned long should be 64-bit wide. That code won't work as-is on other OSes or on 32-bit so it should be fine. It's hacky research code :D
1
Replying to @yo_yo_yo_jbo
This is all for now but there will be more details in March :)
1
3
Replying to @yo_yo_yo_jbo
That's where I got the idea yeah 😆
1
13
github.com/google/security-r… Our newest research project is finally public! We can load malicious microcode on Zen1-Zen4 CPUs!
A bit late but here is a recording of the mix I did for the LakeCTF 2024 finals (lakectf.epfl.ch). 6 hours of my favorite peak time and minimal techno, enjoy! soundcloud.com/nspace-877713…
2
21
🇪🇺🗳️:✅ 🥳
6
Replying to @0xbbjubjub
Did Deutsche Bahn have other plans for you?
Replying to @spendergrsec
Do you have any suggestions on what benchmarks to run? 🙂 I asked in the lkml thread but no one replied
1
2
Replying to @antoniofrighez
Yeah. I don't want to call it type isolation because you can still have objects of two different types in the same cache and confuse between them.
Replying to @antoniofrighez
This is not type isolation, it prevents attackers from confusing between objects allocated in two different caches. It's a prerequisite for type isolation and similar mitigations