Skip to content

[Snyk] Security upgrade firebase-admin from 8.10.0 to 13.10.0 - #352

Open
caniszczyk wants to merge 1 commit into
mainfrom
snyk-fix-ba0750620ac22d346babc710151f1a98
Open

[Snyk] Security upgrade firebase-admin from 8.10.0 to 13.10.0#352
caniszczyk wants to merge 1 commit into
mainfrom
snyk-fix-ba0750620ac22d346babc710151f1a98

Conversation

@caniszczyk

Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • builders/testdata/nodejs/functions/firebase_post_3.4.0_yarn/package.json
  • builders/testdata/nodejs/functions/firebase_post_3.4.0_yarn/yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Improper Verification of Cryptographic Signature
SNYK-JS-NODEFORGE-19635204
  721  

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

…age.json & builders/testdata/nodejs/functions/firebase_post_3.4.0_yarn/yarn.lock to reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-NODEFORGE-19635204
@caniszczyk

Copy link
Copy Markdown
Author

Merge Risk: High

This is a significant major version upgrade from v8 to v13, introducing substantial breaking changes that require major code refactoring and environment updates.

Key Breaking Changes:

  • Mandatory API Refactoring (v10.0.0): The SDK has transitioned from a namespaced API to a modular, tree-shakable API. This is a fundamental change that requires rewriting all interactions with the library. [1, 9]

    • Old Pattern: const admin = require('firebase-admin'); admin.auth().getUser(uid);
    • New Pattern: const { getAuth } = require('firebase-admin/auth'); getAuth().getUser(uid);
  • Multiple Node.js Version Requirements: Support for older Node.js versions has been dropped across several major releases. You must ensure your environment meets the minimum requirement for the target version.

    • v10.0.0 requires Node.js 12 or higher. [1]
    • v11.0.0 requires Node.js 14 or higher. [2]
    • Newer versions have continued to increase this requirement. The CLI, for example, dropped Node.js 16 support at its v13. [3]
  • API Deprecations and Removals: Methods have been deprecated and removed in favor of new ones, such as the sendAll function in Cloud Messaging being replaced by sendEach in v12. [11]

Recommendation:
This upgrade cannot be performed with simple find-and-replace changes. It requires a dedicated migration effort to adopt the new modular API structure and to ensure the runtime environment is compatible. It is highly recommended to consult the official Firebase migration guides before proceeding.

Source: Firebase Admin SDK Release Notes, Upgrade to v10 Guide

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

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

Successfully merging this pull request may close these issues.

3 participants