browserify-sign vulnerabilities

adds node crypto signing for browsers

Registry
npm
Latest
4.2.6
License
ISC
Source
github.com/crypto-browserify/browserify-sign (opens the source repository in a new tab)

1 known advisory

The latest version, 4.2.6, is not affected by any of them. Projects on older versions may be.

Update to the latest version:npm install browserify-sign@4.2.6

Security advisories for browserify-sign

  • HighGHSA-x9w5-v3q2-3rhw26 Oct 2023

    browserify-sign upper bound check issue in `dsaVerify` leads to a signature forgery attack

    Affected
    >=2.6.0 <4.2.2
    Fixed in
    4.2.2

Which of your client projects still run an old browserify-sign?

NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

Other npm packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.