Skip to content

[Snyk] Fix for 4 vulnerabilities#11893

Open
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-75d49b8eb9ad49e466d1a89e82237281
Open

[Snyk] Fix for 4 vulnerabilities#11893
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-75d49b8eb9ad49e466d1a89e82237281

Conversation

@q1blue
Copy link
Collaborator

@q1blue q1blue commented Feb 8, 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/search-backend-module-techdocs/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 Arbitrary Code Injection
SNYK-JS-BACKSTAGEPLUGINTECHDOCSNODE-15166604
  225  
high severity Directory Traversal
SNYK-JS-BACKSTAGEPLUGINTECHDOCSNODE-15166605
  149  
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235959
  84  
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235969
  84  

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:

🦉 Arbitrary Code Injection
🦉 Directory Traversal
🦉 Server-side Request Forgery (SSRF)


EntelligenceAI PR Summary

This PR pins Backstage dependencies to specific versions in the search-backend-module-techdocs plugin package.json.

  • Replaced workspace protocol references with explicit version numbers for four dependencies
  • @backstage/backend-common pinned to version 0.24.1
  • @backstage/plugin-catalog-common pinned to version 0.1.0
  • @backstage/plugin-search-common pinned to version 0.3.1
  • @backstage/plugin-techdocs-node pinned to version 1.13.11
  • Change enables stricter dependency control and prepares package for potential publication

@codesandbox
Copy link

codesandbox bot commented Feb 8, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@gemini-code-assist
Copy link

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, focuses on enhancing the security posture of the project by upgrading key dependencies within the plugins/search-backend-module-techdocs package. The updates target and resolve four identified vulnerabilities, including critical issues like arbitrary code injection and directory traversal, ensuring a more secure and stable application environment.

Highlights

  • Dependency Updates for Security: Several @backstage dependencies in plugins/search-backend-module-techdocs/package.json have been updated from workspace:^ to specific versions to address security vulnerabilities.
  • Vulnerability Remediation: This pull request aims to fix 4 identified vulnerabilities, including high-severity Arbitrary Code Injection and Directory Traversal, and low-severity Server-side Request Forgery issues.
  • Manual yarn.lock Update Required: The yarn.lock file was not automatically updated by Snyk, requiring a manual yarn command execution to ensure consistency, especially for projects using zero-installs.
Changelog
  • plugins/search-backend-module-techdocs/package.json
    • Updated @backstage/backend-common from workspace:^ to 0.24.1.
    • Updated @backstage/plugin-catalog-common from workspace:^ to 0.1.0.
    • Updated @backstage/plugin-search-common from workspace:^ to 0.3.1.
    • Updated @backstage/plugin-techdocs-node from workspace:^ to 1.13.11.
Activity
  • This pull request was automatically created by Snyk to address security vulnerabilities.
  • Snyk identified 4 vulnerabilities, including high-severity Arbitrary Code Injection and Directory Traversal, and low-severity Server-side Request Forgery.
  • A warning was issued that the yarn.lock file failed to update and requires manual intervention.
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.

@snyk-io
Copy link

snyk-io bot commented Feb 8, 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.

@socket-security
Copy link

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
License policy violation: npm atob under CC-BY-3.0

License: CC-BY-3.0 - the applicable license policy does not allow this license (4) (package/LICENSE.DOCS)

From: ?npm/atob@2.1.2

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/atob@2.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@entelligence-ai-pr-reviews
Copy link

Walkthrough

This pull request updates the dependency management strategy for the search-backend-module-techdocs plugin by replacing workspace protocol references with explicit version numbers for four Backstage packages. The changes pin @backstage/backend-common to 0.24.1, @backstage/plugin-catalog-common to 0.1.0, @backstage/plugin-search-common to 0.3.1, and @backstage/plugin-techdocs-node to 1.13.11. This modification moves away from workspace-relative versioning to fixed version specifications, which typically indicates preparation for package publication or ensures stricter dependency compatibility control.

Changes

File(s) Summary
plugins/search-backend-module-techdocs/package.json Updated four Backstage package dependencies from workspace protocol references to explicit version numbers: @backstage/backend-common to 0.24.1, @backstage/plugin-catalog-common to 0.1.0, @backstage/plugin-search-common to 0.3.1, and @backstage/plugin-techdocs-node to 1.13.11.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Build as Build System
    participant Module as search-backend-module-techdocs
    participant BC as backend-common (0.24.1)
    participant PCC as plugin-catalog-common (0.1.0)
    participant PSC as plugin-search-common (0.3.1)
    participant PTN as plugin-techdocs-node (1.13.11)
    
    Note over Build,PTN: Dependency Version Update (package.json only)
    
    Build->>Module: Install dependencies
    Module->>BC: Resolve @backstage/backend-common@0.24.1
    Module->>PCC: Resolve @backstage/plugin-catalog-common@0.1.0
    Module->>PSC: Resolve @backstage/plugin-search-common@0.3.1
    Module->>PTN: Resolve @backstage/plugin-techdocs-node@1.13.11
    
    Note over Module: Dependencies changed from<br/>workspace:^ to fixed versions
    
    BC-->>Module: Dependency resolved
    PCC-->>Module: Dependency resolved
    PSC-->>Module: Dependency resolved
    PTN-->>Module: Dependency resolved
    Module-->>Build: Module ready with updated dependencies
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

@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 automated Snyk pull request attempts to fix four vulnerabilities by updating dependencies. However, the changes are critically flawed: several key packages are downgraded to outdated major versions, which will likely break the application. Furthermore, the yarn.lock file is not updated, compromising build reproducibility and the effectiveness of the patch. I recommend rejecting this PR and addressing the vulnerabilities manually.

Comment on lines +39 to +49
"@backstage/backend-common": "0.24.1",
"@backstage/backend-plugin-api": "workspace:^",
"@backstage/backend-tasks": "workspace:^",
"@backstage/catalog-client": "workspace:^",
"@backstage/catalog-model": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/plugin-catalog-common": "workspace:^",
"@backstage/plugin-catalog-common": "0.1.0",
"@backstage/plugin-permission-common": "workspace:^",
"@backstage/plugin-search-backend-node": "workspace:^",
"@backstage/plugin-search-common": "workspace:^",
"@backstage/plugin-techdocs-node": "workspace:^",
"@backstage/plugin-search-common": "0.3.1",
"@backstage/plugin-techdocs-node": "1.13.11",

Choose a reason for hiding this comment

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

critical

This automated dependency update has several critical issues and should be reverted.

  1. Major dependency downgrades: This change downgrades several @backstage packages to much older major versions, which will almost certainly introduce breaking changes and regressions. For example:

    • @backstage/plugin-catalog-common is downgraded from a version compatible with 1.0.15 to 0.1.0.
    • @backstage/plugin-search-common is downgraded from a version compatible with 1.2.5 to 0.3.1.

    These downgrades suggest that the Snyk tool may have had trouble resolving the correct dependency versions within the yarn workspace (workspace:^).

  2. yarn.lock not updated: The PR description states that yarn.lock was not updated. This is a critical problem as it means the dependency tree is not locked, and builds will not be reproducible. The vulnerabilities might not even be fixed without the lock file update.

It is strongly recommended to address the vulnerabilities manually by finding appropriate versions that do not introduce breaking changes, likely by updating the packages within the monorepo to newer, non-vulnerable versions and continuing to use workspace:^.

    "@backstage/backend-common": "workspace:^",
    "@backstage/backend-plugin-api": "workspace:^",
    "@backstage/backend-tasks": "workspace:^",
    "@backstage/catalog-client": "workspace:^",
    "@backstage/catalog-model": "workspace:^",
    "@backstage/config": "workspace:^",
    "@backstage/plugin-catalog-common": "workspace:^",
    "@backstage/plugin-permission-common": "workspace:^",
    "@backstage/plugin-search-backend-node": "workspace:^",
    "@backstage/plugin-search-common": "workspace:^",
    "@backstage/plugin-techdocs-node": "workspace:^"

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