-
Notifications
You must be signed in to change notification settings - Fork 61
Exposure of Sensitive Information to an Unauthorized Actor #448
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
Comments
We cannot upgrade to v3 of node-fetch since it is now an ESM module. However, we can upgrade to 2.6.7 which contains a backported fix for that vulnerability. But, the octokit modules are unmaintained. Considering that, I am considering maybe pushing a hotfix for this vulnerability |
@wolfy1339: Thank you for clarifying, and thanks in advance for the hotfix. Is there any official line on whether Octokit will be maintained in future or deprecated? It's still listed as the official API library in the GitHub docs and I don't see any mention that it's deprecated in the readme. |
I'm only a volunteer community contributor. I don't have a line to GitHub. Unfortunately, I don't have any further information. |
🎉 This issue has been resolved in version 5.6.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Please update
node-fetch
to fix vulnerability issue:node-fetch <3.1.1 Severity: high node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor - https://github.com/advisories/GHSA-r683-j2x4-v87g
The text was updated successfully, but these errors were encountered: