GitHub Advisoryadvisory · npm
GHSA-c9vv-fhgv-cjc3 agent-js: Insecure Key Generation in `Ed25519KeyIdentity.generate`
CRITICAL
Official page ↗
- Aliases
- CVE-2024-1631
- Ecosystem
- npm
- Packages
- @dfinity/identity, @dfinity/auth-client
- Severity
- Critical
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- Weaknesses
- CWE-321, CWE-330
- Reviewed
- 2024-02-21
Affected packages
• npm @dfinity/identity: >= 0.20.0-beta.0, < 1.0.1 → fixed in 1.0.1
• npm @dfinity/auth-client: >= 0.20.0-beta.0, < 1.0.1 → fixed in 1.0.1
Description
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 use it as the seed to generate the key pair.
Users
Removing a controller of a canister if it's the affected principal
For all canisters you control, fetch the controllers of the canisters using
```sh
dfx canister info --ic
```
If you see the principal `535yc-uxytb-gfk7h-tny7p-vjkoe-i4krp-3qmcl-uqfgr-cpgej-yqtjq-rqe` as one of the controllers, follow the steps below
```sh
dfx identity whoami # record CURRENT_IDENTITY
dfx identity new
dfx identity use
dfx identity get-principal # record NEW_IDENTITY_PRINCIPAL
dfx identity use
dfx canister update-settings --ic --add-controller
dfx canister update-settings --ic --remove-controller `535yc-uxytb-gfk7h-tny7p-vjkoe-i4krp-3qmcl-uqfgr-cpgej-yqtjq-rqe`
```
For more details on canister management, please visit here
Checking funds on wallets / ledgers
If you have funds on ledgers using a browser wallet, please check if the account principal matches `535yc-uxytb-gfk7h-tny7p-vjkoe-i4krp-3qmcl-uqfgr-cpgej-yqtjq-rqe`. If it does, please create a new account and transfer the funds to the new account immediately.
References
1. fix PR link
2. NPM patched version
3. agent-js Github repo
4. agent-js docs
Related
Alias · CVE (1)
- CVE-2024-1631 Impact: The library offers a function to generate an ed25519 key pair via Ed25519KeyIdentity.generate with an optional param to provide a… vulnerability
References
- https://github.com/dfinity/agent-js/security/advisories/GHSA-c9vv-fhgv-cjc3 web
- https://nvd.nist.gov/vuln/detail/CVE-2024-1631 advisory
- https://github.com/dfinity/agent-js/pull/851 web
- https://agent-js.icp.xyz/identity/index.html web
- https://github.com/dfinity/agent-js package
- https://www.npmjs.com/package/@dfinity/identity/v/1.0.1 web