# CVE-2024-45678: Information disclosure in n/a

> Attackers with physical access and specialized equipment can extract ECDSA secret keys from YubiKey devices via electromagnetic side-channel attacks.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2024
- **Updated:** 17 Mar 2025
- **Also known as:** GHSA-cf4q-v7mm-g53q

## What is CVE-2024-45678?

CVE-2024-45678 is a medium-severity vulnerability in n/a, published on 3 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Yubico YubiKey 5 Series devices with firmware before 5.7.0 and YubiHSM 2 devices with firmware before 2.4.0 allow an ECDSA secret-key extraction attack (that requires physical access and expensive equipment) in which an electromagnetic side channel is present because of a non-constant-time modular inversion for the Extended Euclidean Algorithm, aka the EUCLEAK issue. Other uses of an Infineon cryptographic library may also be affected.

Weakness: CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2024-45678?

It affects 18 products.


Products: Yubico Security Key C Nfc by Yubico Firmware, Yubico Security Key Nfc by Yubico Firmware, Yubico Yubihsm 2 Fips Firmware, Yubico Yubihsm 2 Firmware, Yubico Yubikey 5 Nano Fips Firmware, Yubico Yubikey 5 Nano Firmware, Yubico Yubikey 5 Nfc Fips Firmware, Yubico Yubikey 5 Nfc Firmware, Yubico Yubikey 5c Fips Firmware, Yubico Yubikey 5c Firmware, Yubico Yubikey 5c Nano Fips Firmware, Yubico Yubikey 5c Nano Firmware, Yubico Yubikey 5c Nfc Fips Firmware, Yubico Yubikey 5c Nfc Firmware, Yubico Yubikey 5ci Fips Firmware, Yubico Yubikey 5ci Firmware, Yubico Yubikey Bio Firmware, Yubico Yubikey C Bio Firmware.

## How do I fix CVE-2024-45678?

No fix has been published for CVE-2024-45678 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-45678 being exploited?

There is no known exploitation of CVE-2024-45678 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-45678 and fix it if it is affected.

What it is: CVE-2024-45678 is a medium-severity vulnerability in n/a, published on 3 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-45678 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-45678/ (Markdown: https://insights.sbomify.com/CVE-2024-45678/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-45678
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-45678
- OSV: https://osv.dev/vulnerability/CVE-2024-45678

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-45678/
Summaries are generated and may contain mistakes; the official description above is the record.