Vulnerability in hoek package
See original GitHub issueThere is a vulnerability in the hoek
package which is required by hawk
that request depends on.
Request depends on hawk version ~6.0.2
. Updating to hawk version 7.0.0
would fix the problem.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:92
- Comments:29 (1 by maintainers)
Top Results From Across the Web
hoek - npm Package Health Analysis - Snyk
Ensure you're using the healthiest npm packages. Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice.
Read more >How to get rid of the 'hoek' vulnerabilities - Stack Overflow
You should run rm package-lock.json && npm update && npm install , if this still doesn't fix your issue, you can then continue...
Read more >Security Vulnerability of Dependencies for Node.js App ...
For example, to fix the vulnerability in hoek package, just run 'npm install hoek' to install the latest version of hoek. npm audit...
Read more >Auditing package dependencies for security vulnerabilities
Security audits help you protect your package's users by enabling you to find and fix known vulnerabilities in dependencies that could cause data...
Read more >A security vulnerability has been identified in Node.js hoek ...
Node.js hoek is shipped as a component of Data Science Experience Local. Information about a security vulnerability affecting Node.js hoek has been ...
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
yes, hi 👋 hoek maintainer here. version 4.2.1 has been patched. github’s alerts are currently wrong. i’ve submitted a request to correct the version range in the CVE and also harassed some kind folks at github to take care of things on their end. hopefully they’ll stop reporting that version as vulnerable soon.
as far as i understand it, the issue is with a cve, https://nvd.nist.gov/vuln/detail/CVE-2018-3728, regarding
hoek < v5.0.3
;request v2.85.1
requireshawk ~6.0.2
, which requireshoek 4.x.x
.request
requireshawk ~6.0.2
to maintain compatibility with node 4.the cve states that “hoek node module before 5.0.3 suffers from …” and references https://github.com/hapijs/hoek/commit/32ed5c9413321fbc37da5ca81a7cbab693786dee as a fix in
hoek v5.0.3
however,
hoek v4.2.1
also has that fix: https://github.com/hapijs/hoek/commit/5aed1a8c4a3d55722d1c799f2368857bf418d6df https://github.com/hapijs/hoek/blob/v4.2.1/lib/index.js#L116thus, it appears that the cve is incorrectly considering
hoek v4.2.1
as vulnerable and may be why so many github repos are now reporting a vulnerability. i sent an email to nvd.nist.gov about the issue.