Critical Vulnerability CVE-2024-45678 (EUCLEAK) in YubiKey Hardware Security Tokens: A Threat Analysis for Bitcoin Cryptographic Security

21.12.2025

The discovery of vulnerability CVE-2024-45678, known as EUCLEAK, in YubiKey Series 5 hardware security tokens represents one of the most significant cryptographic security incidents of the past decade. This vulnerability, which existed undetected for 14 years and has undergone approximately 80 top-level Common Criteria certifications, exposes critical flaws in the cryptographic library of Infineon Technologies, one of the largest secure element manufacturers in the world. This paper presents a comprehensive scientific analysis of the EUCLEAK attack mechanisms, its technical aspects, and its potential impact on the security of the Bitcoin cryptocurrency, including a detailed examination of electromagnetic side-channel attacks and their implications for modern cryptographic systems.

Critical Vulnerability CVE-2024-45678 (EUCLEAK) in YubiKey Hardware Security Tokens: A Threat Analysis for Bitcoin Cryptographic Security
Yubico YubiKey 5 NFC Security Token, Phishing-Resistant MFA

Technical nature of the CVE-2024-45678 vulnerability and attack classification

Electromagnetic Side-Channel Attack: Scientific Classification

The EUCLEAK vulnerability is  an electromagnetic side  -channel attack, which belongs to a class of  passive physical attacks  on cryptographic systems. In scientific literature, this type of attack is classified as a variant of  TEMPEST attacks  —the US National Security Agency’s codename for methods of intercepting unintentional electromagnetic emissions from electronic devices. More precisely, EUCLEAK belongs to a subcategory of  Differential Electromagnetic Analysis  (DEMA), which uses statistical methods to correlate electromagnetic emissions with cryptographic operations. arxiv+ 7

According to a systematic classification of side-channel attacks proposed in the modern scientific literature, EUCLEAK is characterized by the following parameters: it is  a non-invasive attack  (does not require opening the device for initial analysis),  a local attack  (requires physical proximity to the device), and exploits  the timing characteristics  of cryptographic operations, which are manifested through electromagnetic emissions. The attack exploits  the non-constant-time execution  of the modular inversion in the extended Euclidean algorithm, which creates  an information leak  through timing variations detected as changes in electromagnetic emissions. linkedin+ 5

Cryptographic Foundations of Vulnerability: ECDSA Algorithm and secp256k1

The EUCLEAK vulnerability affects the implementation of  the Elliptic Curve Digital Signature Algorithm  (ECDSA), a fundamental cryptographic primitive in the FIDO protocol and cryptocurrency systems, including Bitcoin. ECDSA exploits the mathematical properties of elliptic curves over finite fields to create digital signatures that provide authentication and data integrity. linkedin+ 5

In the context of Bitcoin, a specific elliptic curve,  secp256k1 , defined by the Standards for Efficient Cryptography Group (SECG), is used. This curve is described by the equation y2=x3+7over a finite field Fp, Where p=2256232977  — a prime number that determines the size of the field. The order of the group of points on this curve is n2256, which provides a 128-bit level of security against known cryptanalytic attacks. github+ 3

The ECDSA signature generation process includes the following steps: generation of an ephemeral random number (nonce) kk , calculating a point on an elliptic curve R=kG  (Where G  — generating point), extraction of coordinate r=xRmodn, and calculating the signature value s=k1(h+rd)modn n , where h  — the message hash, and d  — private key. The critical element is the  modular inversion operation. k1modn, which in the vulnerable Infineon implementation executes with inconsistent timing. keysight+ 4

Extended Euclidean Algorithm and Time Leakage

The vulnerability is localized in the implementation of  the Extended Euclidean Algorithm  (EEA), used to calculate modular inverses. This algorithm calculates the greatest common divisor of two numbers and simultaneously finds the coefficients of the Bézout representation, allowing for the efficient calculation of multiplicative inverses in modular arithmetic. linkedin+ 5

NinjaLab researchers discovered that the EEA implementation in the Infineon cryptographic library exhibits  data- dependent timing  variations. Specifically, the number of algorithm iterations and the execution of conditional branches depend on the bit length and value of the number being inverted. kk . These timing variations, measured with nanosecond precision  , manifest themselves in the electromagnetic emissions characteristics of the microcontroller during cryptographic operations. keysight+ 3

Mathematically, EEA iteratively updates tuples of values (r0,r1,s0,s1,t0,t1), where at each step, a modulo division and a conditional update of variables are performed. The time variability arises because: (1) the number of iterations depends on the bit length of the input data; (2) within each iteration, conditional operations are performed, the timing of which depends on the sign and magnitude of the intermediate values; (3) subtraction and comparison operations are performed a variable number of times. These time leaks create discernible patterns in the electromagnetic emanations, which can be detected and analyzed. arxiv+ 4

EUCLEAK attack methodology and technical requirements

Experimental setup and equipment

A successful EUCLEAK attack requires specialized equipment for recording electromagnetic radiation with high temporal resolution. NinjaLab researchers used a Langer EMV RF-B 3-2 electromagnetic probe (EM probe), an oscilloscope with a sampling rate of at least 1 million samples per second, and specialized signal processing software. The cost of the complete experimental setup, including a laptop for data analysis, is estimated at approximately  $11,000  (approximately €10,000). keysight+ 6

Physical access to the device is a prerequisite for the attack. To obtain the clearest possible signal, an attacker must  open the  YubiKey or other vulnerable device’s casing to place an electromagnetic probe in close proximity to the Infineon SLE78 security microcontroller. While it is theoretically possible to attack through an intact casing using more sensitive equipment, this significantly complicates the process and reduces the signal-to-noise ratio. After data collection is complete, the device can be resealed and returned to the owner with no visible signs of compromise. linkedin+ 7

Key extraction process: theoretical and practical aspects

The EUCLEAK attack consists of several sequential stages.  The first stage  is  the acquisition phase  : the attacker must force the device to perform multiple ECDSA signature operations using the same private key while simultaneously recording electromagnetic emissions. Depending on the attacker’s skill and the system configuration, obtaining a sufficient number of traces requires anywhere from  several minutes to an hour  of physical access to the device. keysight+ 3

The second stage  is  offline analysis  : the collected electromagnetic traces are subjected to complex statistical processing to extract information about the temporal characteristics of the modular inversion. The researchers used bandpass filtering, moving median analysis, and correlation analysis to identify patterns associated with specific bits of the ephemeral key. kk . By analyzing the differences in the duration of individual EEA iterations, one can reconstruct the values ​​of the algorithm’s intermediate variables, which gradually reveals the bits of the nonce kk . arxiv+ 3

The third stage  is  private key recovery : after partial or complete recovery of the nonce kk  of one or more signatures, private key dd  can be calculated mathematically. From the equation of the signature s=k1(h+rd)modn  it follows that d=r1(ksh)modnd = r −1( k ⋅ s − h )mod n . If the nonce was recovered with errors, the researchers used  Pollard’s Kangaroo algorithm  to find the private key in a limited range of possible values. This algorithm for solving the discrete logarithm problem has a time complexity of O(ba), Where [a,b] — a known range, which makes it practical to use when partial information about the key is available. ninjalab+ 5

According to researchers, the offline analysis phase takes approximately  24 hours  when the attack is initially implemented, but can be reduced to  less than one hour  with further optimization of the software and analysis methods. ninjalab+ 3

The scope of the vulnerability and affected devices

Yubico products and firmware versions

All YubiKey 5 Series devices  with firmware prior to 5.7.0  are vulnerable to CVE-2024-45678. This includes the following models: YubiKey 5 NFC, YubiKey 5 Nano, YubiKey 5C, YubiKey 5C Nano, YubiKey 5Ci, and all variants of the YubiKey 5 FIPS Series with firmware prior to 5.7. Additionally,  YubiKey Bio Series devices with firmware prior to 5.7.2  and  Security Key Series devices with firmware prior to 5.7.0 are affected . YubiHSM 2 hardware security modules  with firmware prior to 2.4.0  are also vulnerable. linkedin+ 3

It’s important to note that YubiKey device firmware  cannot be updated  by users. The firmware is installed during manufacturing and remains unchanged for the life of the device. Therefore, the only way to mitigate the vulnerability for users of older models is  to physically replace  the device with a new version running firmware 5.7.0 or higher. Updated versions, which began shipping  on May 21, 2024 , use a new cryptographic library developed by Yubico, which does not contain the EUCLEAK vulnerability. reddit+ 6

Infineon Microcontrollers and Global Distribution

The vulnerability affects  all Infineon security microcontrollers (MCUs ) that use the vulnerable Infineon cryptographic library. This includes the following product families:  Trusted Platform Modules (TPMs)  based on the Infineon Optiga TPM,  the Infineon SLE78 series of secure elements  , and the newer  Infineon Optiga Trust M series . These MCUs are embedded in a wide range of devices, including hardware cryptocurrency wallets from various manufacturers, electronic passports, national ID cards, enhanced-security SIM cards, and smart home and car systems using ECDSA for authentication. linkedin+ 5

According to NinjaLab’s research, the vulnerability existed for  over 14 years  , since approximately 2010. During this period, the vulnerable cryptographic library passed approximately  80 top-level Common Criteria certification assessments  : AVA_VAN.4 levels for TPM modules and AVA_VAN.5 for other protected elements. This demonstrates fundamental problems in the security certification process, where sophisticated side-channel attacks can remain undetected even by the most stringent assessments. ninjalab+ 6

Potential impact on Bitcoin security

Bitcoin Security Architecture and the Role of ECDSA

The Bitcoin cryptocurrency relies on the ECDSA algorithm with the secp256k1 curve as a fundamental cryptographic primitive for securing transactions and controlling ownership of digital assets. Each Bitcoin user generates a key pair:  a private key dd  is a random 256-bit number from the range [1,n1], Where n — the order of the group of points on secp256k1, and  the public key Q=dG, Where G — a generating point of the curve. The public key is hashed to create  a Bitcoin address to which funds can be sent. github+ 4

When making a transaction, the owner of the funds must create a digital signature proving possession of the private key corresponding to the sending address. This signature is generated using ECDSA and verified by Bitcoin network nodes to confirm the transaction’s legitimacy. Compromise of the private key means  complete loss of control  over all funds associated with the corresponding address, with no possibility of recovery. bitcoin+ 5

EUCLEAK Attack Scenarios for Bitcoin Wallets

The EUCLEAK vulnerability poses a serious threat to users of hardware cryptocurrency wallets built on vulnerable Infineon microcontrollers. While the specific wallet models affected by the attack have not been comprehensively tested, researchers indicate that  any device using Infineon security microcontrollers with the vulnerable cryptographic library for ECDSA operations is potentially vulnerable. ninjalab+ 4

The attack scenario involves the following steps: (1) the attacker gains  temporary physical access  to the victim’s hardware wallet, such as through theft and return, interception during delivery, or insider trading; (2) the device is opened and an electromagnetic probe is placed to record signals during signature transactions; (3) the attacker initiates multiple transaction signatures, which may require knowledge of the device’s PIN, if set, or exploitation of additional vulnerabilities to bypass authentication; (4) once a sufficient number of electromagnetic traces have been collected, the device is resealed and returned to the owner; (5) the private key is extracted offline within 1-24 hours; (6) the attacker creates and signs a transaction transferring all funds from the compromised address to an address controlled by the attacker. reddit+ 8

Limitations of the attack’s practical application

Despite the theoretical seriousness of the threat, the practical application of the EUCLEAK attack against Bitcoin wallets faces several significant limitations. First, the attack requires  physical access  to the device for a period of several minutes to an hour, making it unsuitable for remote attacks. Second, the need for  expensive specialized equipment  (approximately $11,000) and high technical expertise in cryptography and electrical engineering significantly limits the pool of potential attackers. linkedin+ 8

Third, many modern hardware wallets require  physical confirmation  of transactions on the device and the entry of a PIN or biometric authentication. If these security mechanisms are implemented correctly, an attacker will not be able to force the device to perform signature transactions without knowing the PIN or bypassing biometrics, significantly complicating the data collection phase. Fourth, following the discovery of the vulnerability in September 2024, hardware wallet manufacturers began migrating to alternative secure elements or updated versions of Infineon microcontrollers with a patched cryptographic library. reddit+ 7

It’s also important to note that the vulnerability only affects  signature operations performed on the vulnerable device. Bitcoin addresses created using other methods (such as software wallets based on BIP32/BIP39 deterministic hierarchical wallets running on devices without vulnerable Infineon microcontrollers) are not vulnerable to the EUCLEAK attack. Furthermore, the Bitcoin protocol itself and the ECDSA cryptographic algorithm remain secure—the vulnerability is related solely to the specific implementation of modular inversion in the Infineon cryptographic library. keysight+ 7

Context of other Bitcoin cryptographic vulnerabilities

The EUCLEAK vulnerability should be considered in the context of other known cryptographic issues affecting the security of Bitcoin private keys. One of the most serious historical issues was  nonce reuse  in ECDSA signatures. If two different messages are signed using the same ephemeral key, kk , the private key can be trivially calculated from the two signatures by solving a system of linear equations modulo nn . sciencedirect+ 3

A 2017 analysis of Bitcoin transactions by researchers found that approximately  0.48% of signatures  were affected by the weak randomness issue, leading to the compromise of  1,331 private keys . This issue was partially mitigated by the introduction of  RFC 6979  , a standard for deterministic nonce generation that eliminates the reliance on a random number generator and makes the signing process reproducible and free of nonce reuse. Most modern Bitcoin implementations, including Bitcoin Core, have adopted RFC 6979, significantly reducing the risk of key leakage through weak randomness. reddit+ 2

Another category of attacks includes  lattice attacks  and  partial  nonce disclosure attacks. If several bits of the nonce kk  leaks through various channels (e.g., timing attacks, side-channel attacks, or implementation bugs), a lattice structure can be constructed that allows the full private key to be recovered using the LLL (Lenstra–Lenstra–Lovász) algorithm or the Pollard kangaroo algorithm. EUCLEAK, by its nature, represents precisely this type of attack—partial disclosure of nonce information through timing characteristics manifested in electromagnetic emissions. keysight+ 5

Countermeasures and protection prospects

Software countermeasures: constant-time implementations

A fundamental defense against timing side-channel attacks, including EUCLEAK, is  constant-time programming  . This approach requires that the execution time of critical cryptographic operations be  independent of the secret data values ​​processed by the algorithm. In the context of ECDSA, this means that the operations of nonce generation, modular inversion, scalar multiplication on an elliptic curve, and the final signature computation must all execute in the same time, regardless of the bit values ​​of the private key and the ephemeral key. arxiv+ 6

Various techniques can be used to achieve constant time in modular inversion. One approach is to use  an algorithm based on Fermat’s little theorem : computing k1modnk −1mod n  as kn2modnn −2mod n  using fast constant-time exponentiation. This method guarantees a fixed number of operations regardless of the value of kk , but can be computationally more expensive than optimized variants of the extended Euclidean algorithm. An alternative approach is to create  a constant-time version of the EEA , where all conditional jumps are replaced by arithmetic operations using masks, and the number of iterations is fixed and equal to the worst-case yp+ 2

Additional techniques include  masking  and  blinding  . Masking introduces random values ​​that algebraically mask secret data throughout the computation and are then removed at the end, ensuring the correct result. For modular inversion, this might mean computing (rk)1modnr ⋅ k )−1mod n , where rr  is a random number and then multiply the result by rr  to receive k1k −1. Blinding the ephemeral key during signature computation can also effectively mask the timing characteristics from an attacker. gistre.epita+ 3

Hardware countermeasures and secure elements

At the hardware level, protection against electromagnetic side-channel attacks can include  electromagnetic shielding  of the microcontroller, the use of  dual-rail logic  that consumes constant power regardless of the data being processed, and  noise injection  into power and clock signals to mask information leaks. Faraday cages can effectively block electromagnetic radiation, but their practical application in small consumer devices like the YubiKey presents technological and economic challenges. halborn+ 6

Modern  Secure Elements  (SEs) and  Hardware Security Modules  (HSMs) are designed to withstand physical attacks. They include built-in countermeasures against power analysis, electromagnetic analysis, fault injection, and other forms of attack. Certification to  Common Criteria EAL5+  or  FIPS 140-2/140-3 Level 3+  requires demonstrating resistance to a wide range of side-channel attacks. However, as the EUCLEAK case demonstrates, even devices that have achieved the highest levels of certification can contain subtle vulnerabilities that are detectable using advanced analysis techniques. ninjalab+ 6

Architectural approaches in the Bitcoin ecosystem

From an architectural perspective, the Bitcoin ecosystem can employ several strategies to minimize the risks associated with side-channel attacks on hardware wallets.  Multi-signature (multi-sig) configurations  , where signatures from multiple independent keys stored on different devices or platforms are required to authorize a transaction, can significantly enhance security. Even if one key is compromised via an EUCLEAK attack, funds remain secure until the attacker gains access to a sufficient number of other keys. coinspect+ 3

Hierarchical Deterministic Wallets (HD wallets) comply   with the BIP32/BIP39/BIP44 standards to generate multiple addresses from a single seed phrase. When implemented correctly, compromising one child key should not reveal the master key or other child keys. However, this depends on the use of  hardened derivations  , which provide cryptographic separation between keys. github+ 2

Temporary key rotation  and  limiting address reuse  are best practices that also mitigate risks. If each Bitcoin address is used only once, and funds are regularly moved to new, independently generated addresses, the window of opportunity for an attacker to compromise a specific key is significantly reduced. It’s also important to upgrade hardware wallets to models with patched microcontrollers and use only devices from trusted manufacturers with transparent vulnerability disclosure and update processes. coolwallet+ 4

Conclusion: EUCLEAK’s Lessons for the Crypto Industry

The discovery of vulnerability CVE-2024-45678 in YubiKey hardware tokens and other devices based on Infineon microcontrollers represents an important precedent in the field of cryptographic security. The fact that this critical vulnerability remained undetected for 14 years and has undergone nearly 80 top-tier certifications demonstrates the fundamental limitations of current security assessment processes. This underscores the need for more rigorous testing methodologies specifically aimed at detecting subtle side-channel attacks, as well as the importance of continually reviewing and updating certification standards. linkedin+ 8

The scientific classification of EUCLEAK as an electromagnetic side-channel attack exploiting the variable execution time of the extended Euclidean algorithm fits into the broader context of research into the security of cryptographic implementations. This reminds the industry that theoretically secure cryptographic algorithms can be compromised through vulnerabilities in their practical implementations, especially when constant-time programming principles are not followed. arxiv+ 7

For the Bitcoin ecosystem, the threat posed by EUCLEAK is moderate, given the high barriers to attack: the need for physical access, expensive equipment, and technical expertise. However, users of hardware cryptocurrency wallets based on vulnerable Infineon microcontrollers should consider migrating to updated devices and implementing multi-layered security strategies, such as multi-signature and hierarchical deterministic wallets. reddit+ 7

More broadly, the EUCLEAK incident highlights the critical importance of transparency, responsible disclosure of vulnerabilities, and collaboration between security researchers, hardware manufacturers, software developers, and certification authorities. Only through such collaboration can the cryptographic industry effectively counter constantly evolving threats and ensure reliable protection of digital assets and personal data in today’s interconnected world. ninjalab+ 3

  1. https://www.linkedin.com/posts/rishab-valiyaveedu-00b241207_cve-2024-45678-also-known-as-the-eucleak-activity-7284966966140833795-Pu2X
  2. https://www.yubico.com/support/security-advisories/ysa-2024-03/
  3. https://ninjalab.io/eucleak/
  4. https://arxiv.org/html/2512.07292v1
  5. https://www.arxiv.org/abs/2512.07292
  6. https://www.sciencedirect.com/topics/computer-science/side-channel
  7. https://en.wikipedia.org/wiki/Tempest_(codename)
  8. https://cybersnowden.com/side-channel-attacks/
  9. https://en.wikipedia.org/wiki/Side-channel_attack
  10. https://greydynamics.com/tempest-electronic-spying-and-countermeasures/
  11. https://www.startupdefense.io/cyberattacks/tempest-attack
  12. https://www.keysight.com/blogs/en/tech/nwvs/2024/09/24/security-highlight-side-channel-vulnerability-in-infineon-cryptographic-library
  13. https://ninjalab.io/wp-content/uploads/2024/10/20241022_eucleak.pdf
  14. https://perso.uclouvain.be/fstandae/PUBLIS/34.pdf
  15. https://arxiv.org/pdf/1611.03748.pdf
  16. https://github.com/bitcoin-core/secp256k1/blob/master/README.md
  17. https://www.nervos.org/knowledge-base/secp256k1_a_key%20algorithm_(explainCKBot)
  18. https://en.bitcoin.it/wiki/Elliptic_Curve_Digital_Signature_Algorithm
  19. https://learnmeabitcoin.com/technical/cryptography/elliptic-curve/
  20. https://bitcoinwiki.org/wiki/secp256k1
  21. https://learnmeabitcoin.com/technical/cryptography/elliptic-curve/ecdsa/
  22. https://blog.gistre.epita.fr/posts/cyril.barbel-2024-09-09-using_side-channel_attack_to_extract_secret_key_from_yubikey_5_series/
  23. https://www.ewadirect.com/proceedings/ace/article/view/10087
  24. https://cr.yp.to/talks/2007.05.28/slides.pdf
  25. https://ninjalab.io/wp-content/uploads/2024/09/20240903_eucleak.pdf
  26. https://www.helpnetsecurity.com/2024/09/04/yubico-security-keys-vulnerability/
  27. https://www.infosecurity-magazine.com/news/researcher-vulnerability-yubikeys/
  28. https://www.reddit.com/r/netsec/comments/1f86qtf/eucleak_is_a_sidechannel_vulnerability_that/
  29. https://www.securityweek.com/crypto-vulnerability-allows-cloning-of-yubikey-security-keys/
  30. https://cryptodeeptech.ru/kangaroo/
  31. https://en.wikipedia.org/wiki/Pollard’s_kangaroo_algorithm
  32. https://www.mat.uniroma2.it/~eal/teske.pdf
  33. https://www.nitrokey.com/news/2024/nitrokeys-offer-investment-security-without-infineons-security-vulnerability
  34. https://vulners.com/cve/CVE-2024-45678
  35. https://www.reddit.com/r/yubikey/comments/1hzayxk/i_bought_a_new_yubikey_5_in_december_2024_and/
  36. https://www.reddit.com/r/yubikey/comments/1f9b1n3/faq_new_security_issue_found_by_ninjalab/
  37. https://www.reddit.com/r/yubikey/comments/1j3p5q3/yubikey_security_issues/
  38. https://www.reddit.com/r/yubikey/comments/1ff2eus/new_firmware/
  39. https://cybernews.com/security/researchers-clone-yubikeys-other-microchips-may-be-flawed/
  40. https://indico.math.cnrs.fr/event/11948/attachments/5546/9591/0_thomas_roche.pdf
  41. https://www.sciencedirect.com/science/article/abs/pii/S0167739X17330030
  42. https://kudelskisecurity.com/research/polynonce-a-tale-of-a-novel-ecdsa-attack-and-bitcoin-tears
  43. https://www.scirp.org/journal/paperinformation?paperid=92905
  44. https://www.coinspect.com/blog/hardware-wallet-security/
  45. https://hackaday.com/2019/09/13/side-channel-attack-shows-vulnerabilities-of-cryptocurrency-wallets/
  46. https://www.logintc.com/blog/what-is-the-yubikey-vulnerability/
  47. https://www.scworld.com/news/yubikey-5-devices-open-to-cloning-via-side-channel-attacks
  48. https://www.ledger.com/academy/series/enter-the-donjon/episode-2-side-channel-attacks
  49. https://www.coolwallet.io/blogs/blog/hardware-wallet-secure-element-the-complete-guide
  50. https://www.reddit.com/r/Bitcoin/comments/1j24hh3/nonce_r_reuse_and_bitcoin_private_key_security_a/
  51. https://cryptodeeptech.ru/lattice-attack/
  52. https://www.reddit.com/r/Bitcoin/comments/76ql3e/serious_vulnerability_found_are_there_infineon/
  53. https://en.wikipedia.org/wiki/Timing_attack
  54. https://docs.aqtiveguard.com/kb-articles/timing-attacks-and-broader-side-channel-attacks/
  55. https://stellarix.com/insights/articles/mitigation-techniques-of-side-channel-attacks/
  56. https://dl.acm.org/doi/10.1007/978-3-031-25319-5_5
  57. https://core.ac.uk/download/pdf/157762438.pdf
  58. https://www.halborn.com/blog/post/top-5-security-threats-of-hardware-wallets
  59. https://tropicsquare.com/blogs/hardware-security-understanding-the-differences-between-a-secure-element-tpm-hsm-and-a-tee
  60. https://blog.trailofbits.com/2018/11/27/10-rules-for-the-secure-use-of-cryptocurrency-hardware-wallets/
  61. https://www.swissbit.com/en/support/security-advisories/sb-2024-01/
  62. https://cvefeed.io/vuln/detail/CVE-2024-45678
  63. https://www.reddit.com/r/yubikey/comments/1k0qnxb/issues_with_yubikey_firmware_574_and_site/
  64. https://vulners.com/vulnrichment/VULNRICHMENT:CVE-2024-45678
  65. https://euvd.enisa.europa.eu/vulnerability/CVE-2024-45678
  66. https://www.vicarius.io/vsociety/vulnerabilities/cve-2024-45678
  67. https://www.heise.de/en/news/EUCLEAK-More-products-vulnerable-to-cloning-attack-10079927.html
  68. https://github.com/advisories/GHSA-cf4q-v7mm-g53q
  69. https://pnltc.org/article/security-advisory-ysa-2024-03
  70. https://dl.acm.org/doi/10.1145/2976749.2978353
  71. https://en.wikipedia.org/wiki/ROCA_vulnerability
  72. https://www.linkedin.com/posts/dlaskov_hacking-embedded-infineon-activity-7339708235672621056-ipod
  73. https://www.jstage.jst.go.jp/article/transfun/advpub/0/advpub_2023VLP0010/_pdf
  74. https://bugzilla.mozilla.org/show_bug.cgi?id=1631583
  75. https://it4sec.substack.com/p/a-flaw-in-infineons-security-microcontrollers
  76. https://summerschool-croatia.cs.ru.nl/2023/slides/Jan_slides.pdf
  77. https://www.zach.be/p/the-most-secure-chip-in-the-world
  78. http://library.usc.edu.ph/ACM/SIGSAC%202017/ccs/p1626.pdf
  79. https://en.wikipedia.org/wiki/Electromagnetic_attack
  80. https://coingeek.com/vulnerabilities-found-crypto-hardware-wallets/
  81. https://arxiv.org/pdf/1804.08714.pdf
  82. https://cs-people.bu.edu/tromer/acoustic/
  83. https://www.vice.com/en/article/how-white-hat-hackers-stole-crypto-keys-from-an-offline-laptop-in-another-room/
  84. https://ieeexplore.ieee.org/iel8/6287639/10380310/10630786.pdf
  85. https://ieeexplore.ieee.org/document/10115517/
  86. https://en.bitcoin.it/wiki/Secp256k1
  87. https://bitcoinops.org/en/topics/side-channels/
  88. https://www.ijert.org/research/implementation-of-rsa-algorithm-secure-against-timing-attacks-using-fpga-IJERTV2IS120657.pdf
  89. http://www.scielo.org.mx/scielo.php?script=sci_arttext&pid=S1405-55462024000401879
  90. https://ir.library.oregonstate.edu/downloads/fn106z04s
  91. https://www.sciencedirect.com/science/article/abs/pii/S0167926025000963
  92. https://univagora.ro/jour/index.php/ijccc/article/view/2780/1057
  93. https://www.youtube.com/watch?v=QyIoi1tth2U
  94. https://perso.uclouvain.be/fstandae/PUBLIS/42.pdf
  95. https://www.ledger.com/why-secure-elements-make-a-crucial-difference-to-hardware-wallet-security
  96. https://citeseerx.ist.psu.edu/document?repid=rep1&type=pdf&doi=3e13eb97ce4790907e2784fceb7e563f2b5a2e0f
  97. https://botan.randombit.net/handbook/side_channels.html
  98. https://www.rambus.com/blogs/side-channel-attacks/
  99. http://www.diva-portal.org/smash/get/diva2:828995/FULLTEXT01.pdf
  100. https://www.cryptrec.go.jp/exreport/cryptrec-ex-1047-2002.pdf
  101. https://en.wikipedia.org/wiki/Side_channel
  102. https://www.giac.org/paper/gsec/4287/tempest-electromagnetic-emanations-security-government-standard/106943
  103. https://crypto.stanford.edu/~dabo/papers/ssl-timing.pdf
  104. https://www.cl.cam.ac.uk/~mgk25/ih98-tempest.pdf
  105. https://csrc.nist.gov/csrc/media/events/physical-security-testing-workshop/documents/papers/physecpaper19.pdf
  106. https://ru.wikipedia.org/wiki/%D0%90%D1%82%D0%B0%D0%BA%D0%B0_%D0%BF%D0%BE_%D1%81%D1%82%D0%BE%D1%80%D0%BE%D0%BD%D0%BD%D0%B8%D0%BC_%D0%BA%D0%B0%D0%BD%D0%B0%D0%BB%D0%B0%D0%BC
  107. https://www.ndss-symposium.org/wp-content/uploads/ndss2021_4B-2_23021_paper.pdf
  108. https://www.reddit.com/r/Bitcoin/comments/1ny2eqm/why_dont_wallet_softwares_like_electrum_and/
  109. https://www.morpher.com/blog/ecdsa-in-cryptocurrency-security
  110. https://www.tokenmetrics.com/blog/best-hardware-wallets-for-security-2025
  111. https://trezor.io
  112. https://www.huntress.com/cybersecurity-101/topic/secure-element-application
  113. https://www.yubico.com/authentication-standards/fido2/
  114. https://cryptopals.com/sets/8/challenges/58.txt
  115. https://hideez.com/blogs/news/fido2-explained
  116. https://www.startupdefense.io/cyberattacks/side-channel-attack
  117. https://www.microsoft.com/en-us/security/business/security-101/what-is-fido2
  118. https://cryptodeep.ru/kangaroo/
  119. https://arxiv.org/pdf/2109.09461.pdf
  120. https://www.descope.com/learn/post/fido2
  121. https://github.com/JeanLucPons/Kangaroo
  122. https://dl.acm.org/doi/10.1145/3645109
  123. https://fidoalliance.org/specifications/
  124. https://github.com/deviant101/Side-Channel-Attacks-Countermeasures
  125. https://www.robin-data.io/en/data-protection-and-data-security-academy/wiki/passwordless-authentication-over-fido2
  126. https://www.sciencedirect.com/science/article/pii/S0166218X02005905
  127. https://indigo.uic.edu/articles/thesis/Cryptographic_Security_Countermeasures_against_Side-Channel_Attacks/10835738/files/19343285.pdf