-
-
Notifications
You must be signed in to change notification settings - Fork 27k
Resolving High Severity Vulnerabilities in a React App Using npm Audit and npm Fix #13130
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
Labels
Comments
One work around was to add the overrides in your package.json file.
|
See #11174 |
3 tasks
hkjn
added a commit
to hkjn/lnhw
that referenced
this issue
Jun 18, 2023
Found via facebook/create-react-app#13130 (comment), this allows us to avoid the security vulnerability warning for react-scripts library by upgrading the transitive css-select => nth-check dependency to >= v2.0.1 for facebook/create-react-app#11174.
hkjn
added a commit
to hkjn/lnhw
that referenced
this issue
Jun 18, 2023
This workaround for the facebook/create-react-app#11174 warning for react-scripts library upgrades the transitive css-select => nth-check dependency to >= v2.0.1. Found via facebook/create-react-app#13130 (comment).
hkjn
added a commit
to hkjn/lnhw
that referenced
this issue
Jun 18, 2023
This workaround for the facebook/create-react-app#11174 warning for react-scripts library upgrades the transitive css-select => nth-check dependency to >= v2.0.1. Found via facebook/create-react-app#13130 (comment).
hkjn
added a commit
to hkjn/lnhw
that referenced
this issue
Jun 18, 2023
This workaround for the facebook/create-react-app#11174 warning for react-scripts library upgrades the transitive css-select => nth-check dependency to >= v2.0.1. Found via facebook/create-react-app#13130 (comment).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I'm getting a high severity vulnerability in my postergenius project. The npm audit report shows that nth-check version is below 2.0.1, which has an inefficient Regular Expression Complexity. The report suggests running npm audit fix --force, but warns that it will install [email protected], which is a breaking change.
Did you try recovering your dependencies?
yes, I've tried recovering my dependencies by deleting node_modules, package-lock.json, and yarn.lock files, and running npm install. However, the issue still persists.
Which terms did you search for in User Guide?
I searched for "vulnerability", "npm audit", "dependency recovery", and "npm force update" in the User Guide.
Environment
Environment:
OS: Windows 10
Node: 16.13.1
npm: 8.1.0
Yarn: Not installed
webpack: Not installed
Steps to reproduce
Expected behavior
I expect to see no high severity vulnerabilities in the audit report.
Actual behavior
The audit report shows a high severity vulnerability in nth-check package.
Reproducible demo
https://github.com/klawrenceboxx/AI-Posters
Steps to reproduce:
Clone the postergenius-demo project from GitHub.
Run npm install in the project directory to install dependencies.
Run npm audit in the project directory to see the audit report.
The text was updated successfully, but these errors were encountered: