-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
word-wrap vulnerable to Regular Expression Denial of Service #40
Comments
Just encountered this as well as latest firebase-admin package is reliant on some packages that in turn is reliant on |
Dealing with this as well. Any ETA on patch release? |
Per this PR: They aren't able to merge in due to bus factor and the original repo owner getting hit by a bus. As a hack, they've published a new version under another package name. Par for the course in JS community... |
As seen here #33 (comment)
It appears this is currently a maintained version which you can override with. |
This unfortunately breaks
|
I'm also on eslint 8.43.0 - is it possible there is some cache left-overs? |
No, retried from clean as well. Ended up adding an override for optionator instead, which accomplishes the same thing effectively:
|
Interesting - pleased you found your solution too. |
Any updates? |
npm audit doesn't fix it for me.. unfortunately. Any update on the solution? |
The best solution we have right now (from here) is to switch to a patched fork. #33 (comment) "resolutions": {
"word-wrap": "npm:@aashutoshrathi/word-wrap@^1.2.4"
}, Looks like "resolutions": {
"optionator": "^0.9.3"
} Non-Yarn users can use Lastly, it seems many have swapped over to the fork according to the fork's page on npmjs.org. |
By overriding `optionator` version per jonschlinkert/word-wrap#40 (comment) This only affects puppeteer, a test library, so no need to cut a new app release. There was no app security issue but fixing this reduces noise that could distract from new, actual security issues. Also `npm update` generally.
Duplicate of #32 |
Hi, everyone. I was looking for an answer, and never thought it would be as simple as this.
It will ultimately update the version of the dependency package and it creates no problem. For reference of the change, you can see here |
Fixed in |
All versions of the package word-wrap are vulnerable to Regular Expression Denial of Service (ReDoS) due to the usage of an insecure regular expression within the result variable.
The text was updated successfully, but these errors were encountered: