security vulnerability in dependency tree
See original GitHub issueIssue Description
nsp caught this and fails our builds –
codecov@3.0.0
> request@2.81.0
> hawk@3.1.3
> hoek@2.x.x
I think updating request
should fix the issue.
hoek
:
https://nodesecurity.io/advisories/566
Vulnerable <= 4.2.0 || >= 5.0.0 < 5.0.3
Patched > 4.2.0 < 5.0.0 || >= 5.0.3
Issue Analytics
- State:
- Created 5 years ago
- Reactions:8
- Comments:6
Top Results From Across the Web
Vulnerabilities in Dependencies: What You Need to Know
The risk of using dependencies with known vulnerabilities has been included in the OWASP top 10 list of security risks. It has been...
Read more >Investigate Dependencies in the Application Dependency Tree
LFX Security looks for vulnerabilities in your open-source dependencies and identifies the vulnerabilities. The Dependency Tree dashboard provides detailed ...
Read more >Fixing vulnerabilities found in a dependency tree - ITNEXT
Fixing vulnerabilities found in a dependency tree. I'm working for a company that produces financial cloud solutions. We're making a new app ...
Read more >78% of vulnerabilities are found in indirect dependencies ...
Snyk has scanned over a million snapshot projects and has discovered that vulnerabilities in indirect dependencies account for 78% of ...
Read more >How to identify vulnerable dependencies in a Maven project
In this article, we will dicuss how to configure and use the dependency-check-maven plugin to audit our Maven project for known security ...
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
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for the update. Fixes in 3.0.4
This is on the @github security alert system now so anyone who owns a project which uses this module anywhere in their dependency tree will being getting alerts.