CVE-2024-1631
Published: 21 February 2024
Summary
CVE-2024-1631 is a critical-severity Use of Hard-coded Cryptographic Key (CWE-321) vulnerability in Dfinity Icp-Js-Core. Its CVSS base score is 9.1 (Critical).
Operationally, ranked in the top 17.1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-0614
Vulnerability details
Impact: The library offers a function to generate an ed25519 key pair via Ed25519KeyIdentity.generate with an optional param to provide a 32 byte seed value, which will then be used as the secret key. When no seed value is provided,…
more
it is expected that the library generates the secret key using secure randomness. However, a recent change broke this guarantee and uses an insecure seed for key pair generation. Since the private key of this identity (535yc-uxytb-gfk7h-tny7p-vjkoe-i4krp-3qmcl-uqfgr-cpgej-yqtjq-rqe) is compromised, one could lose funds associated with the principal on ledgers or lose access to a canister where this principal is the controller.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Proper key establishment and management processes directly preclude embedding static cryptographic keys in source code or binaries.
Supply chain protection includes scrutiny of cryptographic implementations, reducing hard-coded keys planted by untrusted vendors.
Functional and assurance requirements specified in acquisition can prohibit hard-coded cryptographic keys in delivered products.
Approved PKI issuance and trust stores replace ad-hoc or hard-coded keys with properly managed, signed certificates.
Assessments can uncover and prevent suppliers from shipping components that contain hard-coded cryptographic keys.