Podcast
Root Causes 381: Apple Chip Sideloading Attack Leaks Encryption Keys
Hosted by
Jason Soroko
Fellow
Original broadcast date
April 26, 2024
A newly revealed side channel attack enables theft of private keys from M-series Apple chips. We explain.
Podcast transcript
Lightly edited for flow and brevity.
TCTim CallanOkay. So I'm looking at an article. I don't think this is the only place this was reported, but it's the one I'm looking at. It's an Ars Technica article from Dan Goodin. We get a lot of our stories from Dan. March 21, 2024 is the date and the headline reads: Unpatchable Vulnerability in Apple Chip Leaks Secret Encryption Keys. And so when I see the word secret and the word encryption key, it gets my attention. And the word leak. So um, what went on here, Jason?
So Tim, what we are referring to, let's talk about it, Apple, as you know, has come up with their own chipsets for a lot of their laptops. So you'll find MacBook Pros, MacBook Airs, with the new M series chips and what we're talking about here is I think mostly the M1 and M2 generations. There is an M3 at this point in time. So what is going on, Tim, of course, is that some researchers, very good research, has been able to recreate private keys stored in memory. So this is a good old-fashioned side channel attack. And it is caused by - Tim, you're gonna love this.
From what I can tell the root cause of what's going on here is that the optimization - - anytime you're hearing about side channel attacks, quite often what's going on is some sort of memory or process optimization that's leaking information. And isn’t it interesting that in this case, these Apple M1 and M2 chips they're using this new feature, right, the abbreviation DMP. It's not important right now. What's important is that this DMP optimization feature is mistaking private key, of course, and if any of you've ever seen these things, these things are usually hashed so it's a series of alphanumeric characters. Right, Tim?
TCTim CallanRight.
TCTim CallanSo side channel attacks, these are hard, right?
TCTim CallanLike, they're like, like fundamentally, you're looking at the behavior of the chip. And I don't know if this is based on power, or sound or heat. I guess most of the time it's power, but I’m given to understand that dealing with a side channel check isn't that trivial, because you have to somehow obscure the information that is being used in the side channel attack. And that’s a difficult thing, because you're talking about something like the amount of power that it's consuming where you can't really stop consuming the power you need to consume.
TCTim CallanSo if this is based on listening to chip optimizations, does that mean that these chips are going to have to become less optimal in order to solve this particular vulnerability? Are they going to have to go back and somehow wind back or mitigate these optimizations that are here to make the chip ultimately run faster?
TCTim CallanOkay. Good.
TCTim CallanYep. Okay. So we've talked about side channel attacks before. I think we'll talk about them again. One of the interesting thing about side channel attacks, of course, is they are a side channel. So that vulnerability can sneak by the design process. Sometimes I think a little more easily than another kind of vulnerability because you do have to be very lateral in you're thinking about how to protect from this kind of information gathering.
TCTim CallanWell, don't let any GoFetch on your system, Jay.
TCTim CallanGood tip. Pro tip. All right. Well, thank you very much, Jay. This has been Root Causes.