Skip to content

Conversation

@Trott
Copy link
Member

@TrottTrott commented Jul 2, 2021

path-parse 1.0.6 is vulnerable to ReDoS. Update to 1.0.7. Uh, not that a
ReDoS is likely to affect us in this tool.

Refs: jbgutierrez/path-parse@09e1086

@TrottTrott added the request-ci Add this label to start a Jenkins CI on a PR. label Jul 2, 2021
@github-actionsgithub-actionsbot added tools Issues and PRs related to the tools directory. and removed request-ci Add this label to start a Jenkins CI on a PR. labels Jul 2, 2021
@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

path-parse 1.0.6 is vulnerable to ReDoS. Update to 1.0.7. Uh, not that a ReDoS is likely to affect us in this tool. Refs: jbgutierrez/path-parse@09e1086 PR-URL: nodejs#39232 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Zijian Liu <[email protected]>
@Trott
Copy link
MemberAuthor

Trott commented Jul 4, 2021

Landed in 2d542f5

@TrottTrott merged commit 2d542f5 into nodejs:masterJul 4, 2021
@TrottTrott deleted the path-parse branch July 4, 2021 14:42
targos pushed a commit that referenced this pull request Jul 11, 2021
path-parse 1.0.6 is vulnerable to ReDoS. Update to 1.0.7. Uh, not that a ReDoS is likely to affect us in this tool. Refs: jbgutierrez/path-parse@09e1086 PR-URL: #39232 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Zijian Liu <[email protected]>
@targostargos mentioned this pull request Jul 13, 2021
targos pushed a commit that referenced this pull request Sep 4, 2021
path-parse 1.0.6 is vulnerable to ReDoS. Update to 1.0.7. Uh, not that a ReDoS is likely to affect us in this tool. Refs: jbgutierrez/path-parse@09e1086 PR-URL: #39232 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Zijian Liu <[email protected]>
@targostargos mentioned this pull request Sep 4, 2021
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

toolsIssues and PRs related to the tools directory.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@Trott@nodejs-github-bot@targos@Lxxyx