-
Notifications
You must be signed in to change notification settings - Fork 900
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
Known vulnerability in undici subdependency #8038
Labels
Comments
m-wagner98
added
new
A new issue that hasn't be categoirzed as question, bug or feature request
question
labels
Feb 22, 2024
jbalidiong
added
needs-attention
and removed
new
A new issue that hasn't be categoirzed as question, bug or feature request
labels
Feb 22, 2024
Hi @m-wagner98, thanks for bringing this to our attention. Let me communicate this with our engineers to update the dependency to the patched version. I’ll update this thread if I have any information to share. |
In case it helps, the Steps to reproduce is just |
DellaBitta
pushed a commit
that referenced
this issue
Feb 27, 2024
See GHSA-3787-6prv-h9w3 For reference, `undici` is used to polyfill `fetch` in our Node bundles, as we are not restricting Node support to 18+ yet. Fixes #8038
Merged
tom-andersen
pushed a commit
that referenced
this issue
Jul 24, 2024
See GHSA-3787-6prv-h9w3 For reference, `undici` is used to polyfill `fetch` in our Node bundles, as we are not restricting Node support to 18+ yet. Fixes #8038
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Operating System
n/a
Browser Version
n/a
Firebase SDK Version
10.8.0
Firebase SDK Product:
Auth, Firestore, Functions, Storage
Describe your project's tooling
Angular app, built with ionic.
Describe the problem
The CI/CD pipeline fails because SonarQube detected a known vulnerability in the undici subdependency:
GHSA-3787-6prv-h9w3
Steps and code to reproduce issue
Perform a SonarQube scan with the owasp dependency check plugin on a package.json where the "firebase": "^10.8.0" entry is present.
The text was updated successfully, but these errors were encountered: