Our work on ring interconnect side channel attacks was accepted at @USENIXSecurity 2021 (#usesec21)! Full paper and source code are now available at: arxiv.org/pdf/2103.03443…
Context: Multicore CPUs have many components (agents) that communicate with each other. The ring interconnect is what many Intel CPUs use to move data between these components (e.g., during a memory access).
In our paper, we reverse engineer the architecture of such ring interconnect. Read our paper to learn more than you ever thought you wanted to know about how the Intel CPU ring interconnect works, down to arbitration policies, protocols and physical implementation.
We describe, for the first time, the necessary and sufficient conditions to create "ring contention". Such contention occurs when multiple agents contend on the ring interconnect and suffer small delays in their memory accesses.
We show how the above conditions can be used to build a cross-core covert channel with a capacity of over 4 Mbps from a single thread, the largest to date for a cross-core covert channel that does not rely on shared memory.
Finally, we show two examples of side channel attacks that exploit ring contention. The first attack leaks key bits from vulnerable EdDSA and RSA implementations. The second attack infers the precise timing of keystrokes typed by a victim user.
Importantly, unlike prior attacks, our attacks do *not* rely on sharing memory, cache sets, core-private resources or any specific uncore structures. As a consequence, they are hard to mitigate using existing "domain isolation" techniques.

• • •

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

Keep Current with Riccardo Paccagnella

Riccardo Paccagnella 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!

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

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

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!