-
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CVE-2021-3803 (High) detected in nth-check-1.0.2.tgz - autoclosed #2116
Comments
ℹ️ This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #2128 |
Sorry, friend. As far as this ol' bot can tell, your issue does not properly use one of this repo's available issue templates. Please try again, if you like. (And if I'm confused, please let us know. 😬)
|
This issue is potentially a duplicate of one of the following issues:
|
👋 Thanks for reporting! |
This issue is potentially a duplicate of one of the following issues:
|
Thank you for your report, the issue you have reported has just been fixed.
|
This old thread has been automatically locked. If you think you have found something related to this, please open a new issue by following the issue guide (https://github.com/AlexRogalskiy/typescript-tools/blob/master/.github/ISSUE_TEMPLATE/bug_report.md), and link to this old issue if necessary. |
CVE-2021-3803 - High Severity Vulnerability
performant nth-check parser & compiler
Library home page: https://registry.npmjs.org/nth-check/-/nth-check-1.0.2.tgz
Path to dependency file: typescript-tools/package.json
Path to vulnerable library: typescript-tools/node_modules/nth-check/package.json
Dependency Hierarchy:
Found in HEAD commit: dabf1fb3bd94ffd02d8da6cefcebc90694579f87
nth-check is vulnerable to Inefficient Regular Expression Complexity
Publish Date: 2021-09-17
URL: CVE-2021-3803
Base Score Metrics:
Type: Upgrade version
Origin: fb55/nth-check@v2.0.0...v2.0.1
Release Date: 2021-09-17
Fix Resolution: nth-check - v2.0.1
Step up your Open Source Security Game with WhiteSource here
The text was updated successfully, but these errors were encountered: