Vulnerability (low severity) introduced by `find-node-modules`
See original GitHub issueThe braces
npm module is vulnerable to Regular Expression Denial of Service (ReDoS).
The braces
module is a dependency of commitizen
via
- commitizen@2.9.6
- find-node-modules@1.0.4
- findup-sync@0.4.2
- micromatch@2.3.11
- braces@1.8.5
- micromatch@2.3.11
- findup-sync@0.4.2
- find-node-modules@1.0.4
There is no new version of findup-sync
or find-node-modules
available that comes with a braces
version >= 2.3.1
to fix the vulnerability.
I suggest using a package other than find-node-modules
for the required functionality.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
"found 1 low severity vulnerability" warning while creating ...
Describe the bug While creating React-App using npx create-react-app command this warning comes: found 1 low severity vulnerability run `npm ...
Read more >Vulnerability Severity Levels - Invicti
Vulnerability Severity Levels indicate the seriousness of detected issues. Each vulnerability has a different impact; some are urgent, while others are less ...
Read more >Vulnerability Metrics - NVD
NVD Vulnerability Severity Ratings. NVD provides qualitative severity ratings of "Low", "Medium", and "High" for CVSS v2.0 base score ranges in addition to ......
Read more >Vulnerability management rules - Prisma - Palo Alto Networks
As you build out your policy, you'll create rules that filter out insignificant information, such as low severity vulnerabilities, and surface vital ...
Read more >Low Severity Vulnerabilities - Acunetix
Low Severity Vulnerabilities · Vulnerability Categories · Abuse Of Functionality · Acumonitor · Arbitrary File Creation · Authentication Bypass · Bruteforce Possible ...
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
Thanks for bringing this up btw. Generally speaking I am not likely to move off a module but would rather put in the PRs to get it up to date. We rely on their functionality so we should contribute back through PRs. If there is a PR that isn’t being merged for a long time that we need merged then we could have that conversation.
We’re good. Thanks all! ❤️