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

Regular Expression Denial of Service bug with node-fetch prior to version 3.2.10 #1512

Open
marck283 opened this issue Sep 29, 2023 · 0 comments
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@marck283
Copy link

marck283 commented Sep 29, 2023

Thanks for stopping by to let us know something could be better!

PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.

  1. Is this a client library issue or a product issue?
    This issue is related to the client library for Node.js.

  2. Did someone already solve this?

  • This issue is solved in node-fetch@3.2.10.
  1. Do you have a support contract?
    No.

If the support paths suggested above still do not result in a resolution, please provide the following details.

Environment details

  • OS: Windows 11
  • Node.js version: 20.7.0
  • npm version: 10.1.0
  • gax-nodejs version: 3.6.1

Steps to reproduce

  1. Create a new Node.js project
  2. Install node-fetch versions ranging between 3.1.0 and 3.2.9 or packages that depend on such versions of node-fetch.

This bug affects all versions of node-fetch from 3.1.0 until 3.2.9.

Making sure to follow these steps will guarantee the quickest resolution possible.

Thanks!

@marck283 marck283 added priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Sep 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

1 participant