Security: Upgrade boom and hawk to fix hoek
See original GitHub issueVersions
v1.7.4
Repro steps
CLI currently uses old Boom
and Hawk
dependencies, which loads an old version of Hoek
which is vulnerable.
Desired behavior
Upgrade to latest Boom
and Hawk
.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:32
- Comments:24 (1 by maintainers)
Top Results From Across the Web
How to get rid of the 'hoek' vulnerabilities - Stack Overflow
I really want to fix the security issues. How do I get rid of the pesky 'hoek' vulnerabilities? node.js · angular · github...
Read more >Karma npm - Vulnerabilities & Security Analysis - Snyk
Find out if karma has security vulnerabilities that can threaten your software project, ... Remediation. Upgrade hoek to versions 4.2.1, 5.0.3 or higher....
Read more >Npm WARN when building for production - Meteor forums
When I build my meteor app for production, I see the following npm warnings… npm WARN deprecated hawk@3.1.3: This module moved to @hapi/hawk...
Read more >Github – Proper way to fix potential security vulnerability in a ...
( rm package-lock.json is only if it exists.) Edit: In yet a 3rd app, I checked npm outdated and found I had to...
Read more >Unable to use DOMO CLI (App Dev Studio) — Dojo Community
Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at...
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 Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Potential regression - vulnerable lib still installed with
@angular/cli@^6.0.3
runningng new-app
GitHub’s automated vulnerability checking is now finding and reporting this, both by email and on the repository page. Please reopen.