npm audit security vulnerability in node-forge
See original GitHub issueNpm audit
indicates a vulnerability in the node-forge dependency.
=== npm audit security report ===
│ High │ Prototype Pollution in node-forge │
│ Package │ node-forge │
│ Patched in │ >= 0.10.0 │
│ Dependency of │ actions-on-google │
│ Path │ actions-on-google > googleapis > googleapis-common > │
│ │ google-auth-library > gtoken > google-p12-pem > node-forge │
│ More info │ https://npmjs.com/advisories/1561
Issue Analytics
- State:
- Created 3 years ago
- Reactions:18
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Vulnerability detected in node-forge - Stack Overflow
I've run npm audit fix. node-forge is only in my package-lock.json file and is required by "selfsigned" dependency. node ...
Read more >Fixing security vulnerabilities in npm dependencies in less ...
2.1) To fix any dependency, you need to first know which npm package depends on that. npm audit. This will tell you the...
Read more >node-forge - Snyk Vulnerability Database
version published direct vulnerabilities
1.3.1 29 Mar, 2022 0. C. 0. H. 0. M. 0. L
1.3.0 17 Mar, 2022 0. C. 0. H. 0....
Read more >Auditing package dependencies for security vulnerabilities
A security audit is an assessment of package dependencies for security vulnerabilities. Security audits help you protect your package's users by enabling ...
Read more >NPM Audit: How to Scan Packages for Security Vulnerabilities
Node Package Manager (npm) is a popular utility that allows JavaScript developers to create, use, reuse, manage, and share small pieces of ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@digitaltoast https://github.com/actions-on-google/assistant-conversation-nodejs is used for conversation action using Action Builder with the new Action SDK, while this repository is still relevant for Smart Home actions.
Looks like the vulnerability in this repository would require a major version upgrade for the
google-auth-library
:while would in turn transitively change the node engine requirements from:
to:
This seems like a reasonable change to me since both Node.js 6 and 8 are not actively supported anymore by the Node.js project: https://nodejs.org/en/about/releases/, but would require a major version bump of the library itself.
Is there any update on this? Please fix the security issues!