Skip to content
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

High Severity CVE found in cachable-request <10.2.7 #8661

Closed
6 of 7 tasks
ajrice6713 opened this issue Feb 13, 2023 · 3 comments
Closed
6 of 7 tasks

High Severity CVE found in cachable-request <10.2.7 #8661

ajrice6713 opened this issue Feb 13, 2023 · 3 comments
Labels
closed: please-fix-this-cve This issue is asking for fixing a CVE in a build-only dep which doesn't pose any real threat. status: needs more information There is not enough information to take action on the issue.

Comments

@ajrice6713
Copy link
Contributor

Have you read the Contributing Guidelines on issues?

Prerequisites

  • I'm using the latest version of Docusaurus.
  • I have tried the npm run clear or yarn clear command.
  • I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
  • I have tried creating a repro with https://new.docusaurus.io.
  • I have read the console error message carefully (if applicable).

Description

A high-severity CVE has been found in cachable-request, which @docusaurus-core and @docusaurus-preset-classic depend on.

Please see the CVE notice for more information, as this vulnerability leaves a DDOS vulnerability open.

Reproducible demo

No response

Steps to reproduce

N/A

Expected behavior

cachable-request version bumped to v10.2.7

Actual behavior

N/A

Your environment

  • Public source code:
  • Public site URL:
  • Docusaurus version used:
  • Environment name and version (e.g. Chrome 89, Node.js 16.4):
  • Operating system and version (e.g. Ubuntu 20.04.2 LTS):

Self-service

  • I'd be willing to fix this bug myself.
@ajrice6713 ajrice6713 added bug An error in the Docusaurus core causing instability or issues with its execution status: needs triage This issue has not been triaged by maintainers labels Feb 13, 2023
@slorber slorber added status: needs triage This issue has not been triaged by maintainers closed: please-fix-this-cve This issue is asking for fixing a CVE in a build-only dep which doesn't pose any real threat. and removed status: needs triage This issue has not been triaged by maintainers labels Feb 15, 2023
@Josh-Cena
Copy link
Collaborator

Josh-Cena commented Feb 15, 2023

Could you give the dependency graph? cachable-request is not found in either our own repo or a newly scaffolded user site. There's also a close-to-100% chance it won't impact anything—see #6394 —but we need more information to be able to assess the risk or know how to fix it.

@Josh-Cena Josh-Cena added status: needs more information There is not enough information to take action on the issue. and removed status: needs triage This issue has not been triaged by maintainers labels Feb 15, 2023
@slorber
Copy link
Collaborator

slorber commented Feb 15, 2023

🤷‍♂️ can't find it either

Also the link provided does not work (anymore) but this was a regexp DDOS which is unlikely to affect us anyway. We can close immediately and reopen if it is really a security issue.

@slorber slorber closed this as not planned Won't fix, can't repro, duplicate, stale Feb 15, 2023
@Josh-Cena Josh-Cena removed the bug An error in the Docusaurus core causing instability or issues with its execution label Feb 15, 2023
@ajrice6713
Copy link
Contributor Author

Huh - even our dependabot PR has been withdrawn for this CVE. Ive never seen that happen before

Regardless - thanks for taking a look, looks like no action is needed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: please-fix-this-cve This issue is asking for fixing a CVE in a build-only dep which doesn't pose any real threat. status: needs more information There is not enough information to take action on the issue.
Projects
None yet
Development

No branches or pull requests

3 participants