Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2024-1631

Vulnerability in @dfinity/identity (CVE-2024-1631)

Summary

Vulnerability in @dfinity/identity (CVE-2024-1631). Confidential information can be exposed externally. Exploitable via Ed25519KeyIdentity.generate. Mitigation: upgrade to 1.0.1 or later.

Original description

The description as published by the source.

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, 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. Users are asked to take proactive measures mentioned below in Workarounds:Users to protect their assets.

Patches

Patch for the vulnerability is available in v1.0.1 for all the packages listed in the advisory. Please upgrade and deploy your canisters immediately.

Workarounds

Developers

The recommended fix is to upgrade the package to the patched version. If that is not possible, there are couple of workarounds to handle the insecure key generation.

  1. Invoking the function as Ed25519KeyIdentity.generate(null) would fix the broken conditional evaluation and force the function to generate a securely random seed. However, this is not guaranteed to work for future upgrades.
  2. Passing a securely generated randomness as a seed to Ed25519KeyIdentity.generate would force the library to us…

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2024-1631 has been found in @dfinity/identity.
Attackers can target a specific entry point like Ed25519KeyIdentity.generate over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade @dfinity/identity to 1.0.1 or later.
If unsure, ask your IT team or search "@dfinity/identity CVE-2024-1631" on the vendor's site.

CVE-2024-1631 (@dfinity/identity) — CWE-321
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Ed25519KeyIdentity.generate
Patched: 1.0.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-321) exists in @dfinity/identity. Attackers reach the vulnerable code path via Ed25519KeyIdentity.generate without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of @dfinity/identity. Attack surface: Ed25519KeyIdentity.generate.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 1.0.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@dfinity/identity' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@dfinity/identity' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @dfinity/identity を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade @dfinity/identity to 1.0.1

    ステージング環境で 1.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @dfinity/identity
[{"type":"SEMVER","events":[{"introduced":"0.20.0-beta.0"},{"fixed":"1.0.1"}]}]
npm @dfinity/auth-client
[{"type":"SEMVER","events":[{"introduced":"0.20.0-beta.0"},{"fixed":"1.0.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details