-
Notifications
You must be signed in to change notification settings - Fork 40
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
Regular Expression Denial of Service in useragent #3224
Comments
@patphongs @jason-upchurch if the |
@patphongs @lbeaufort |
@patphongs @lbeaufort The |
@jason-upchurch thanks, I agree we should keep an eye out. However, if I'm understanding the vulnerability, it requires user input as the attack vector, which we're not making available to the public. All the input to If that's the case, I think we can remove the due date and security label and bump this issue to a future sprint. |
@jason-upchurch @lbeaufort Did some additional research on this. Because we are using karma under devDependencies, we are not compiling it in the final JS that gets pushed out to production. If you look inside of the |
Moving to sprint 10.4 per @PaulClark2, keeping assigned to me, and I will keep an eye on remediation. |
💯devDependencies are only used at compile-time and don't go to the production server. Only the code in /fec/dist goes to Prod. I'm even less worried about this issue because Karma plays traffic cop during our JavaScript tests ( |
Reached out to SISO to discuss options for path forward. Planning discussion for next week. |
useragent is not used in production code. We will keep an eye on the package for updates nonetheless and update when available or investigate alternative packages if the need arises. Pushing out to Sprint 10.6 for now. |
only used for development, so we don't need this |
Summary
High severity vulnerability found in useragent
Description: Regular Expression Denial of Service (ReDoS)
Info: https://snyk.io/vuln/SNYK-JS-USERAGENT-174737
Introduced through: [email protected]
From: [email protected] > [email protected]
Remediation: None yet
The text was updated successfully, but these errors were encountered: