Live data from Hacker News

CVE-2021-3011: Key recovery on Google Titan Key

ninjalab.io

71–80 of 80 posts

Re: CVE-2021-3011: Key recovery on Google Titan Key

#71
post #15

Something that just crossed my mind is whether this method is destructive or not. Is it possible to steal the key, read it, then give it back to the owner?

The article says they are "cloning" the key, which would imply that yes.

They aren't cloning shit though. They are getting single ECDSA private key after six thousand operations or something.

Re: CVE-2021-3011: Key recovery on Google Titan Key

#73

Note, Google in typical fashion has named 6+ products "Titan." (Titan M, Titan C, Titan Security Key (available in USB A, C, Bluetooth versions), Titan Security Module, OpenTitan, and maybe a few more if you count the old Bluetooth versions that were recalled that look identical to the new Bluetooth version). The various Titan Security Keys are also made by Feitian who sometimes use the same auth chip and sometimes d…

So the titan security keys sold which imply to be secure because they are from google and not that secure? Not secure enough enough to allow bounties for hacking?

It's nice they have a secure chip (titan m) like the secure enclave of apple. But the security keys imply more sense of security as there are not running a lot more apps on this device like on a smartphone.

Re: CVE-2021-3011: Key recovery on Google Titan Key

#74
post #48

> Our work describes a side-channel attack that targets the Google Titan Security Key’s secure element (the NXP A700X chip) by the observation of its local electromagnetic radiations during ECDSA signatures (the core cryptographic operation of the FIDO U2F protocol). In other words, an attacker can create a clone of a legitimate Google Titan Security Key. This is a wildly impressive vuln to discover. Cheers to these…

Indeed it is impressive but not wildly so. Most consumer-ish hardware falls prey to all sorts of various TEMPEST attacks. You can even get started with a HackRF and some inductive loop antennas. It would set you back $130 or so on ebay.

From there, you would have to establish some sort of baseline - that would be the hard part. Once done, you're going to be dealing with amplitude based signals (2ASK primarily). The next step is to determine the frequency the device is running at, and tune to it or 2nd or 3rd harmonics.

From there, it's getting the signal out of the noise, and decoding it for the win.

I've done it a few times. Sorry, I don't have a CVE to my name.

Re: CVE-2021-3011: Key recovery on Google Titan Key

#75
post #32
post #26

Earlier quoted context omitted.

I've been meaning to buy a Yubikey. What is the best practice for using a security key? Is there a mechanism for backing my keys up somewhere safe so that a loss of key doesn't mean a loss of my accounts?

Buy 2. Put one in offsite location (e.g. your notary). I don't have a notary; I got one always in my pocket, and the other one at home in a safe (pickable though). YMMV.

For 99% of humans, an attacker breaking into their home to pick their safe lock is not part of their digital threat model, so that’s pretty sane.

Re: CVE-2021-3011: Key recovery on Google Titan Key

#76

Note, Google in typical fashion has named 6+ products "Titan." (Titan M, Titan C, Titan Security Key (available in USB A, C, Bluetooth versions), Titan Security Module, OpenTitan, and maybe a few more if you count the old Bluetooth versions that were recalled that look identical to the new Bluetooth version). The various Titan Security Keys are also made by Feitian who sometimes use the same auth chip and sometimes d…

security by obscurity bro

Re: CVE-2021-3011: Key recovery on Google Titan Key

#77

I recently rolled out smartcard SSH authentication via PIV on Yubikey NEOs. Since the attack requires a few thousand observations, I’m still quite safe, right? An attacker would still need to know the PIV PIN.

It only affects ECDSA, if it affected RSA or general smartcard security like PIN access it would be an earth-shattering story since it would affect SIM cards, banking cards, satellite CAM cards, you name it. That's why any talk about cloning should't be so casual and misleading, it promotes FUD.

Re: CVE-2021-3011: Key recovery on Google Titan Key

#78

Just curious if anyone knows how long the 4000-6000 observations required would take on this particular device?

Quoting https://arstechnica.com/information-technology/2021/01/hacke... :

> Extracting and later resealing the chip takes about four hours. It takes another six hours to take measurements for each account the attacker wants to hack. In other words, the process would take 10 hours to clone the key for a single account, 16 hours to clone a key for two accounts, and 22 hours for three accounts.

Re: CVE-2021-3011: Key recovery on Google Titan Key

#79
post #75
post #32

Earlier quoted context omitted.

Buy 2. Put one in offsite location (e.g. your notary). I don't have a notary; I got one always in my pocket, and the other one at home in a safe (pickable though). YMMV.

For 99% of humans, an attacker breaking into their home to pick their safe lock is not part of their digital threat model, so that’s pretty sane.

Correct, though could be an insider (friend of a child for example). If my house burns down and my trousers with it I'm toast.
Post reply on HN