Skip to content
This repository has been archived by the owner on Feb 6, 2023. It is now read-only.

Bumps underscore.string to 3.3.5 #2108

Closed

Conversation

claudiopro
Copy link
Contributor

@claudiopro claudiopro commented Jun 16, 2019

Summary

Updates underscore.string to v3.3.5 to mitigate ReDoS vulnerability tracked by esamattis/underscore.string#510

Test Plan

cd website
yarn
yarn start

@claudiopro claudiopro requested a review from NoamELB June 16, 2019 15:25
@claudiopro claudiopro added the security Security issues with Draft.js or its dependencies label Jun 16, 2019
Copy link

@facebook-github-bot facebook-github-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@claudiopro has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

@yangshun
Copy link
Contributor

yangshun commented Jul 3, 2019

I just tried this same approach in Docusaurus 1 core but underscore.string@2.4.0 still remains.

=> Found "remarkable#underscore.string@2.4.0"
info Reasons this module exists
   - "_project_#docusaurus#remarkable#argparse" depends on it
   - Hoisted from "_project_#docusaurus#remarkable#argparse#underscore.string"
info Disk size without dependencies: "76KB"
info Disk size with unique dependencies: "76KB"
info Disk size with transitive dependencies: "76KB"
info Number of shared dependencies: 0

I'm not sure if explicitly bumping underscore.string will help at all. remarkable depends on a very old (pre 1.0.0) version of argparse (argparse": "~0.1.15" in its package.json) and we can't get rid of underscore.string unless remarkable upgrades.

@JoelMarcey
Copy link
Contributor

Is that an issue we can file at https://github.com/jonschlinkert/remarkable re: upgrading?

@claudiopro
Copy link
Contributor Author

@JoelMarcey we should, but the fact that a PR to fix a ReDoS vulnerability has not been responded for two months doesn't give me much hope

I tried to DM Jon on Twitter but he hasn't replied yet 😞

@claudiopro
Copy link
Contributor Author

claudiopro commented Jul 8, 2019

This is tracked by jonschlinkert/remarkable#310 and addressed by jonschlinkert/remarkable#323

@yangshun
Copy link
Contributor

yangshun commented Dec 4, 2019

@claudiopro I think we can close this issue now that we've moved the website to Docusaurus 2

@mrkev mrkev closed this Dec 4, 2019
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
CLA Signed security Security issues with Draft.js or its dependencies
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants