Skip to content

[Snyk] Fix for 4 vulnerabilities#11960

Closed
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-340e64e4ebb0258a51303afd99ae0e39
Closed

[Snyk] Fix for 4 vulnerabilities#11960
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-340e64e4ebb0258a51303afd99ae0e39

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Feb 13, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • plugins/auth-backend/package.json

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.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Prototype Pollution
SNYK-JS-AXIOS-15252993
  170  
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235959
  83  
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235969
  83  
medium severity Allocation of Resources Without Limits or Throttling
SNYK-JS-QS-15268416
  62  

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:

🦉 Prototype Pollution
🦉 Allocation of Resources Without Limits or Throttling
🦉 Server-side Request Forgery (SSRF)


EntelligenceAI PR Summary

This PR updates dependency versions in the auth-backend plugin for improved version control and security.

  • Transitioned internal Backstage packages from workspace protocol to pinned versions (backend-common 0.24.1, catalog-client 0.2.0, config 0.1.1, plugin-auth-node 0.6.0)
  • Upgraded express from ^4.17.1 to ^4.22.0
  • Updated passport-auth0 from ^1.4.3 to ^1.4.4
  • Changes made in plugins/auth-backend/package.json

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 13, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the security posture of the project by resolving several identified vulnerabilities. It achieves this by updating specific package dependencies to their patched versions, ensuring that the application benefits from the latest security fixes without introducing new features or functional changes.

Highlights

  • Security Vulnerability Fixes: This pull request addresses and fixes 4 security vulnerabilities identified by Snyk, including a high-severity Prototype Pollution issue, two low-severity Server-side Request Forgery (SSRF) issues, and a medium-severity Allocation of Resources Without Limits or Throttling vulnerability.
  • Dependency Upgrades: Key dependencies in plugins/auth-backend/package.json have been upgraded to resolve the identified vulnerabilities. This includes specific versions for @backstage/backend-common, @backstage/catalog-client, @backstage/config, @backstage/plugin-auth-node, express, and passport-auth0.
  • Yarn Zero-Install Warning: A warning is included for users utilizing Yarn's zero-install feature, noting that the .yarn/cache/ directory is not updated by this PR and requires a manual yarn run.
Changelog
  • plugins/auth-backend/package.json
    • Updated @backstage/backend-common from workspace:^ to 0.24.1
    • Updated @backstage/catalog-client from workspace:^ to 0.2.0
    • Updated @backstage/config from workspace:^ to 0.1.1
    • Updated @backstage/plugin-auth-node from workspace:^ to 0.6.0
    • Updated express from ^4.17.1 to ^4.22.0
    • Updated passport-auth0 from ^1.4.3 to ^1.4.4
Activity
  • This pull request was automatically created by Snyk to address identified security vulnerabilities.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@github-actions github-actions Bot added the auth label Feb 13, 2026
@snyk-io
Copy link
Copy Markdown

snyk-io Bot commented Feb 13, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@entelligence-ai-pr-reviews
Copy link
Copy Markdown

Walkthrough

This PR updates dependency management in the auth-backend plugin by transitioning from workspace protocol references to pinned versions for internal Backstage packages. The changes include updating @backstage/backend-common to 0.24.1, @backstage/catalog-client to 0.2.0, @backstage/config to 0.1.1, and @backstage/plugin-auth-node to 0.6.0. Additionally, external dependencies are upgraded: express from ^4.17.1 to ^4.22.0 and passport-auth0 from ^1.4.3 to ^1.4.4. These updates improve version control reproducibility and incorporate security patches and bug fixes from the updated packages.

Changes

File(s) Summary
plugins/auth-backend/package.json Updated internal Backstage dependencies from workspace protocol to pinned versions (@backstage/backend-common: 0.24.1, @backstage/catalog-client: 0.2.0, @backstage/config: 0.1.1, @backstage/plugin-auth-node: 0.6.0) and upgraded external dependencies (express: ^4.22.0, passport-auth0: ^1.4.4).

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant Package as auth-backend package.json
    participant Deps as Updated Dependencies
    
    Note over Dev,Deps: Dependency Version Updates
    
    Dev->>Package: Update dependency versions
    
    rect rgb(240, 248, 255)
        Note over Package,Deps: Backstage Internal Dependencies
        Package->>Deps: @backstage/backend-common: 0.24.1
        Package->>Deps: @backstage/catalog-client: 0.2.0
        Package->>Deps: @backstage/config: 0.1.1
        Package->>Deps: @backstage/plugin-auth-node: 0.6.0
    end
    
    rect rgb(255, 248, 240)
        Note over Package,Deps: External Dependencies
        Package->>Deps: express: ^4.22.0 (from ^4.17.1)
        Package->>Deps: passport-auth0: ^1.4.4 (from ^1.4.3)
    end
    
    Note over Dev,Deps: No runtime behavior changes<br/>Only dependency version updates
Loading

▶️AI Code Reviews for VS Code, Cursor, Windsurf
Install the extension

Note for Windsurf Please change the default marketplace provider to the following in the windsurf settings:

Marketplace Extension Gallery Service URL: https://marketplace.visualstudio.com/_apis/public/gallery

Marketplace Gallery Item URL: https://marketplace.visualstudio.com/items

Entelligence.ai can learn from your feedback. Simply add 👍 / 👎 emojis to teach it your preferences. More shortcuts below

Emoji Descriptions:

  • ⚠️ Potential Issue - May require further investigation.
  • 🔒 Security Vulnerability - Fix to ensure system safety.
  • 💻 Code Improvement - Suggestions to enhance code quality.
  • 🔨 Refactor Suggestion - Recommendations for restructuring code.
  • ℹ️ Others - General comments and information.

Interact with the Bot:

  • Send a message or request using the format:
    @entelligenceai + *your message*
Example: @entelligenceai Can you suggest improvements for this code?
  • Help the Bot learn by providing feedback on its responses.
    @entelligenceai + *feedback*
Example: @entelligenceai Do not comment on `save_auth` function !

Also you can trigger various commands with the bot by doing
@entelligenceai command

The current supported commands are

  1. config - shows the current config
  2. retrigger_review - retriggers the review

More commands to be added soon.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request, automatically generated by Snyk, aims to fix four security vulnerabilities by upgrading dependencies. However, the proposed changes have critical issues. The express package is being upgraded to a non-existent version, which will break dependency installation. More importantly, several internal @backstage packages are being pinned to arbitrary versions, including major downgrades, which will likely break the application. This approach is incorrect for a monorepo project. I've left specific comments with suggestions to fix these problems. The changes should be reverted and the vulnerabilities addressed by either updating transitive dependencies within the monorepo or using resolutions.

Comment on lines +35 to +40
"@backstage/backend-common": "0.24.1",
"@backstage/catalog-client": "0.2.0",
"@backstage/catalog-model": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/config": "0.1.1",
"@backstage/errors": "workspace:^",
"@backstage/plugin-auth-node": "workspace:^",
"@backstage/plugin-auth-node": "0.6.0",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

This change replaces workspace:^ with pinned versions for several @backstage packages, introducing major downgrades for some (e.g., @backstage/catalog-client from 1.4.3 to 0.2.0). This will almost certainly break the application. In a monorepo setup like Backstage, workspace:^ is crucial for ensuring local packages are used correctly. Pinning to arbitrary versions from the registry is incorrect and dangerous. Please revert these changes. To fix the underlying vulnerabilities, consider updating the transitive dependencies within the source packages or using resolutions in the root package.json.

Suggested change
"@backstage/backend-common": "0.24.1",
"@backstage/catalog-client": "0.2.0",
"@backstage/catalog-model": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/config": "0.1.1",
"@backstage/errors": "workspace:^",
"@backstage/plugin-auth-node": "workspace:^",
"@backstage/plugin-auth-node": "0.6.0",
"@backstage/backend-common": "workspace:^",
"@backstage/catalog-client": "workspace:^",
"@backstage/catalog-model": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/plugin-auth-node": "workspace:^",

"cookie-parser": "^1.4.5",
"cors": "^2.8.5",
"express": "^4.17.1",
"express": "^4.22.0",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

The specified version ^4.22.0 for the express package does not exist in the npm registry. The latest version is 4.19.2. This will cause dependency installation to fail, which is likely why the yarn.lock file failed to update. Please use a valid version.

Suggested change
"express": "^4.22.0",
"express": "^4.19.2",

@github-actions
Copy link
Copy Markdown

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

@github-actions github-actions Bot added the stale label Feb 20, 2026
@github-actions github-actions Bot closed this Mar 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants