[Snyk] Upgrade firebase-admin from 5.10.0 to 5.13.1#1
Open
armandRobled wants to merge 1 commit intomainfrom
Open
[Snyk] Upgrade firebase-admin from 5.10.0 to 5.13.1#1armandRobled wants to merge 1 commit intomainfrom
armandRobled wants to merge 1 commit intomainfrom
Conversation
Snyk has created this PR to upgrade firebase-admin from 5.10.0 to 5.13.1. See this package in npm: https://www.npmjs.com/package/firebase-admin See this project in Snyk: https://app.snyk.io/org/robledosalazararmando125/project/473f08c5-6aec-4fd7-aeb6-0d424b3cd9ee?utm_source=github&utm_medium=referral&page=upgrade-pr
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade firebase-admin from 5.10.0 to 5.13.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version fixes:
SNYK-JS-Y18N-1021887
Why? Proof of Concept exploit, CVSS 7.3
npm:base64url:20180511
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-AJV-584908
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-AJV-584908
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-HAWK-2808852
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-HAWK-2808852
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-INI-1048974
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-SEMVER-3247795
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-SETVALUE-1540541
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-SETVALUE-450213
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-SETVALUE-1540541
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-SETVALUE-450213
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-TAR-1536528
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-MIXINDEEP-450212
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-TAR-1536531
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-TAR-1579147
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-TAR-1579152
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-TAR-1579155
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-TAR-174125
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-LODASH-1040724
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-DECODEURICOMPONENT-3149970
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-LODASH-450202
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-LODASH-567746
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-LODASH-608086
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-WEBSOCKETEXTENSIONS-570623
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-LODASH-73638
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-FSTREAM-174725
Why? Proof of Concept exploit, CVSS 7.3
npm:deep-extend:20180409
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-GRPC-598671
Why? Proof of Concept exploit, CVSS 7.3
npm:extend:20180424
Why? Proof of Concept exploit, CVSS 7.3
npm:protobufjs:20180305
Why? Proof of Concept exploit, CVSS 7.3
npm:sshpk:20180409
Why? Proof of Concept exploit, CVSS 7.3
npm:atob:20180429
Why? Proof of Concept exploit, CVSS 7.3
npm:node-forge:20180226
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-MINIMIST-559764
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-MINIMIST-559764
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-LODASH-1018905
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-LODASH-73639
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-MINIMATCH-3050818
Why? Proof of Concept exploit, CVSS 7.3
npm:cryptiles:20180710
Why? Proof of Concept exploit, CVSS 7.3
npm:stringstream:20180511
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-MINIMIST-2429795
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-MINIMIST-2429795
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-TAR-1536758
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-KINDOF-537849
Why? Proof of Concept exploit, CVSS 7.3
(*) Note that the real score may have changed since the PR was raised.
Release notes
Package name: firebase-admin
-
5.13.1 - 2018-07-23
- Upgraded Cloud Firestore client to v0.15.4.
- Exposed the Firestore
-
5.13.0 - 2018-07-17
- The Admin SDK can now read the Firebase/Google Cloud Platform project ID from both
- Upgraded the Cloud Firestore client from 0.14.0 to 0.15.2. This version of the Firestore client changes how date values are handled.
- The Admin SDK can now create custom tokens without being initialized with service account credentials.
- The SDK accepts a new
- When deployed in an environment managed by Google (e.g. Google Cloud Functions), the SDK can auto discover a service account ID without any explicit configuration.
- Updated typings of the
- Updated typings of the
-
5.12.1 - 2018-05-15
- Admin SDK now lazy loads all child namespaces and certain heavy dependencies for faster load times. This change also ensures that only the sources for namespaces that are actually used get loaded into the Node.js process.
- Upgraded Cloud Firestore client to v0.14.0.
-
5.12.0 - 2018-04-05
- A new
- A new
- Added the
- Added support for specifying arbitrary key-value fields in the
-
5.11.0 - 2018-03-15
- A new
-
5.10.0 - 2018-03-09
- Upgraded Realtime Database client to v0.2.0. With this upgrade developers can call the
- Upgraded Cloud Firestore client to v0.13.0.
from firebase-admin GitHub release notesTimestamptype from theadmin.firestorenamespace.GCLOUD_PROJECTandGOOGLE_CLOUD_PROJECTenvironment variables.Authentication
serviceAccountIdapp option, which can be used to specify just the client email of a service account.Database
admin.database.Query.once()method to return a more specific type.Cloud Messaging
admin.messaging.WebpushNotificationtype to include all supported notification fields.Authentication
auth.createSessionCookie()method for creating a session cookie from a Firebase ID token.auth.verifySessionCookie()method for validating a given session cookie string.Cloud Messaging
mutableContentoptional field to themessaging.Apstype. This can be used to set themutable-contentproperty when sending FCM messages to APNS targets.messaging.Apstype.Firebase Auth
auth.importUsers()method for importing users to Firebase Auth in bulk.admin.database().ref()method with anotherReferenceinstance as the argument.Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs