-
Notifications
You must be signed in to change notification settings - Fork 9
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
Vulnerable Regular Expressions #10
Comments
Bump |
Anybody working on this issue? Could you @cristianstaicu create a PR with the fix? |
This issue got reported to me through the Node Security Platform: https://nodesecurity.io/advisories/533 |
We don't need `forever` when running in Amazon EC2 Container Service. Also, `forever@0.15.3` depends on `timespan` which has "Regular Expression Denial of Service (ReDoS)" vulnerability: https://snyk.io/vuln/npm:timespan:20170907 There is an issue open for `timespan` here: indexzero/TimeSpan.js#10 (not fixed).
We don't need `forever` when running in Amazon EC2 Container Service. Also, `forever@0.15.3` depends on `timespan` which has "Regular Expression Denial of Service (ReDoS)" vulnerability: https://snyk.io/vuln/npm:timespan:20170907 There is an issue open for `timespan` here: indexzero/TimeSpan.js#10 (not fixed).
Transitive dependency pulled in by Forever. Vulnerability does not affect us because it requires a specially-crafted input string and Forever only ever uses input from the system clock. See: indexzero/TimeSpan.js#10 https://payments-platform.atlassian.net/browse/PP-2687
Transitive dependency pulled in by Forever. Vulnerability does not affect us because it requires a specially-crafted input string and Forever only ever uses input from the system clock. See: indexzero/TimeSpan.js#10 https://payments-platform.atlassian.net/browse/PP-2687
Transitive dependency pulled in by Forever. Vulnerability does not affect us because it requires a specially-crafted input string and Forever only ever uses input from the system clock. See: indexzero/TimeSpan.js#10 https://payments-platform.atlassian.net/browse/PP-2687
Transitive dependency pulled in by Forever. Vulnerability does not affect us because it requires a specially-crafted input string and Forever only ever uses input from the system clock. See: indexzero/TimeSpan.js#10 https://payments-platform.atlassian.net/browse/PP-2687
Transitive dependency pulled in by Forever. Vulnerability does not affect us because it requires a specially-crafted input string and Forever only ever uses input from the system clock. See: indexzero/TimeSpan.js#10 https://payments-platform.atlassian.net/browse/PP-2687
…an:20170907 Transitive dependency pulled in by Forever. Vulnerability does not affect us because it requires a specially-crafted input string and Forever only ever uses input from the system clock. See: indexzero/TimeSpan.js#10 https://payments-platform.atlassian.net/browse/PP-2687
Any estimation, when this will be tackled or fixed? @indexzero @mstum |
Also wondering when this will be fixed... |
The npm 6 tells users about vulnerabilities. Hopefully this gets fixed before that's released with node. |
Bump. Would really like not getting security vulnerability warnings in the console :) |
Just a heads up, I'm not involved in this fork, so I don't know anything more here. |
🛠️ A fix has been provided for this issue. Please reference: 418sec#1 🔥 This fix has been provided through the https://huntr.dev/ bug bounty platform. |
The following regular expressions used for parsing the dates are vulnerable to ReDoS:
The slowdown is relatively large when combining the slowdown produced by all the regexs (for 50,000 characters around 10 seconds matching time). I would suggest one of the following:
If needed, I can provide an actual example showing the slowdown.
The text was updated successfully, but these errors were encountered: