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

Update lockfile to automatically remove the vulnerability introduced by date-and-time@0.13.1 #2

Open
paimon0715 opened this issue Aug 22, 2021 · 1 comment

Comments

@paimon0715
Copy link

Hi, @NilsBaumgartner1994, I have reported a vulnerability in package @google-cloud/storage.

As far as I am aware, vulnerability CVE-2020-26289 detected in package date-and-time<0.14.2 is directly referenced by  @google-cloud/storage@4.7.0, on which your package nsfw-api@1.0.58 transitively depends. As such, this vulnerability can also affect nsfw-api@1.0.58 via the following path:
nsfw-api@1.0.58 ➔ firebase-admin@8.13.0 ➔ @google-cloud/storage@4.7.0 ➔ date-and-time@0.13.1(vulnerable version)

Since @google-cloud/storage has released a new patched version @google-cloud/storage@4.7.2 to resolve this issue (@google-cloud/storage@4.7.2 ➔ date-and-time@0.14.2(fix version)), then this vulnerability patch can be automatically propagated into your project only if you update your lockfile. The following is your new dependency path :
nsfw-api@1.0.58 ➔ firebase-admin@8.13.0 ➔ @google-cloud/storage@4.7.2 ➔ date-and-time@0.14.2(vulnerability fix version).

A warm tip.^_^

@NilsBaumgartner1994
Copy link
Owner

NilsBaumgartner1994 commented Aug 22, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants