browserify-sign vulnerabilities
adds node crypto signing for browsers
- Registry
- npm
- Latest
- 4.2.6
- License
- ISC
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.6Is your project on an affected browserify-sign?
Look after several JavaScript apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for browserify-sign
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
Is your browserify-sign version vulnerable?
- browserify-sign 4.2No known advisories in 4.2.6
- browserify-sign 4.11 advisory in 4.1.0
- browserify-sign 4.01 advisory in 4.0.4
- browserify-sign 3.01 advisory in 3.0.8
- browserify-sign 2.81 advisory in 2.8.0
- browserify-sign 2.71 advisory in 2.7.5
- browserify-sign 2.61 advisory in 2.6.1
- browserify-sign 2.5No known advisories in 2.5.2
- browserify-sign 2.4No known advisories in 2.4.0
- browserify-sign 2.3No known advisories in 2.3.0
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.
Other npm packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.