{"id":287835,"date":"2024-09-04T11:08:50","date_gmt":"2024-09-04T09:08:50","guid":{"rendered":"https:\/\/sftarticles.wpenginepowered.com\/es\/?p=339631"},"modified":"2025-07-01T16:00:22","modified_gmt":"2025-07-01T23:00:22","slug":"dont-worry-yubikeys-are-not-as-vulnerable-as-they-seem","status":"publish","type":"post","link":"https:\/\/cms-articles.softonic.io\/en\/dont-worry-yubikeys-are-not-as-vulnerable-as-they-seem\/","title":{"rendered":"Don’t worry, YubiKeys are not as vulnerable as they seem"},"content":{"rendered":"\n

Recently, a study conducted by NinjaLab has revealed a vulnerability in YubiKey 5, the popular hardware token for two-factor authentication based on the FIDO standard. Although the news may sound alarming, it is important to understand the context and limitations of this vulnerability<\/strong>. Let’s talk about it.<\/p>\n\n\n

\r\n
\r\n
\r\n
\r\n \"TikTok\"\r\n <\/div>\r\n
\r\n TikTok<\/span>\r\n Download<\/a>\r\n <\/div>\r\n
\r\n <\/path><\/path><\/text><\/svg>\r\n <\/div>\r\n <\/div>\r\n
\r\n <\/span>\r\n <\/div>\r\n
\r\n \r\n <\/div>\r\n <\/a>\r\n <\/div>\r\n<\/div>\n\n\n\n

A very technical and targeted attack that we shouldn’t be a target of<\/h2>\n\n\n\n

The discovered vulnerability, of the “side channel” type, affects a microcontroller used in numerous authentication devices, including YubiKey 5. As reported in Arstechnica, the error lies in the implementation of an algorithm used to perform certain mathematical calculations during authentication. NinjaLab researchers demonstrated that, by measuring the electromagnetic radiation emitted during these calculations, they could deduce tiny differences in execution time to discover a crucial component of token security.<\/p>\n\n\n\n

To exploit this vulnerability, therefore, an attacker needs physical access to the YubiKey device<\/strong>. In addition, they must have detailed knowledge of the accounts they want to compromise and specialized equipment to carry out the attack. Even with this, the process is not trivial: it involves both a data collection phase and subsequent analysis that can take several hours. A targeted and highly technical type of attack is very unlikely to affect us.<\/p>\n\n\n\n

Yubico has already responded to this threat. The firmware version 5.7 of the YubiKey<\/strong>, released in May, replaces the cryptographic library with a custom one that is not affected by this vulnerability. Therefore, although we cannot update the units, the ones that come with the firmware are no longer susceptible to this type of attack.<\/p>\n\n\n

\r\n
\r\n
\r\n
\r\n \"TikTok\"\r\n <\/div>\r\n
\r\n TikTok<\/span>\r\n Download<\/a>\r\n <\/div>\r\n
\r\n <\/path><\/path><\/text><\/svg>\r\n <\/div>\r\n <\/div>\r\n
\r\n <\/span>\r\n <\/div>\r\n
\r\n \r\n <\/div>\r\n <\/a>\r\n <\/div>\r\n<\/div>\n\n\n\n

The vulnerability is technically feasible, yes, but the conditions required to exploit it are so restrictive<\/strong> that the majority of YubiKey users should not be affected at all.<\/p>\n","protected":false},"excerpt":{"rendered":"

Recently, a study conducted by NinjaLab has revealed a vulnerability in YubiKey 5, the popular hardware token for two-factor authentication based on the FIDO standard. Although the news may sound alarming, it is important to understand the context and limitations of this vulnerability. Let’s talk about it. A very technical and targeted attack that we … Continue reading “Don’t worry, YubiKeys are not as vulnerable as they seem”<\/span><\/a><\/p>\n","protected":false},"author":9262,"featured_media":287837,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","wpcf-pageviews":2},"categories":[],"tags":[],"usertag":[],"vertical":[],"content-category":[],"class_list":["post-287835","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/posts\/287835","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/users\/9262"}],"replies":[{"embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/comments?post=287835"}],"version-history":[{"count":1,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/posts\/287835\/revisions"}],"predecessor-version":[{"id":311673,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/posts\/287835\/revisions\/311673"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/media\/287837"}],"wp:attachment":[{"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/media?parent=287835"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/categories?post=287835"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/tags?post=287835"},{"taxonomy":"usertag","embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/usertag?post=287835"},{"taxonomy":"vertical","embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/vertical?post=287835"},{"taxonomy":"content-category","embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/content-category?post=287835"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}