Skip to content

← Public intelligence

npm package

@nfid/embed

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Critical, CVSS 9.1npmAmendedPublished

    @nfid/embed has compromised private key due to @dfinity/auth-client producing insecure session keys

    GHSA-84c3-j8r2-mcm8

    Affected
    • npm @nfid/embed >= 0.10.0, < 0.10.1-alpha.6
    Fixed in
    0.10.1-alpha.6· Vendor fix available
    Issue
    Problem User sessions in the @nfid/embed SDK with Ed25519 keys are vulnerable due to a compromised private key 535yc-uxytb-gfk7h-tny7p-vjkoe-i4krp-3qmcl-uqfgr-cpgej-yqtjq-rqe. This exposes users to potential loss of funds on ledgers and unauthorized access to canisters they control. Solution Using version 1.0.1 of @dfinity/auth-client and @dfinity/identity packages, or @nfid/embed 0.10.1-alpha.6 includes patched versions of the issue. User sessions will be automatically fixed when they re-authenticate. Why this happened The DFINITY auth client library provides a function, Ed25519KeyIdentity.generate, for generating an Ed25519 key pair. This function includes an optional parameter to supply a 32-byte seed value, which will be utilized as the secret key. In cases where no seed value is provided, the library is expected to generate the secret key using secure randomness. However, a recent update of DFINITY libraries has compromised this assurance by employing an insecure seed for key…

    Recommended action: Upgrade to 0.10.1-alpha.6 (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →