I'm super happy to share that our work "CustomProcessingUnit: Reverse Engineering and Customization of Intel Microcode" has been accepted at #WOOT23! 🎉
We extend our #BHUSA work to show how microcode tracing and patching can be useful to improve CPU performance and security 👀 Image
+ We trace microcode updates to reverse engineer the secret Intel microcode update algorithm and perform its security evaluation.
+ We present the first x86 PAC implementation, attack it with PACMAN, and provide the first public PAC implementation not vulnerable to the attack.
+ We design a novel breakpoint idea: microcode breakpoints, 1000x faster than software breakpoints, and show their application for fuzzing.
+ We present constant-time hardware division to efficiently protect cryptographic software from side channels on data-dependent operations.
A preprint version of the paper is available at: pietroborrello.com/publication/wo…
And it is all open source!
github.com/pietroborrello…

Amazing collaboration with @cat_easdon @marv0x90 Roland Czerny and @misc0110 😁

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Pietro Borrello

Pietro Borrello Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @borrello_pietro

Aug 9, 2022
Today we disclose ÆPIC Leak: Architecturally Leaking Uninitialized Data from the Microarchitecture 🔥
It is the *first* architectural CPU bug able to leak sensitive data from the cache hierarchy: like an uninitialized read but in the CPU itself.

aepicleak.com Image
It affects 10th, 11th and 12th generation Intel CPUs, where the undefined range in APIC MMIO region returns stale data.
ÆPIC Leak is *not* a transient execution attack: it is a bug in the CPU itself. In our work, we show how it precisely allows us to fully dump enclave in seconds
This has been an amazing collaboration with @0xhilbert @marv0x90 @mlqxyz @lavados @misc0110

Find out more at our BH USA talk tomorrow, and check out our USENIX 22 paper!
paper: aepicleak.com/aepicleak.pdf
github: github.com/IAIK/AEPIC
Read 4 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(