Skip to content

[Snyk] Fix for 4 vulnerabilities#11892

Open
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-a63855bc97ba65a4c38401fb889dc33b
Open

[Snyk] Fix for 4 vulnerabilities#11892
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-a63855bc97ba65a4c38401fb889dc33b

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/techdocs-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 Arbitrary Code Injection
SNYK-JS-BACKSTAGEPLUGINTECHDOCSNODE-15166604
  169  
high severity Directory Traversal
SNYK-JS-BACKSTAGEPLUGINTECHDOCSNODE-15166605
  112  
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 plugin dependencies to explicit versions in the techdocs-backend package, replacing workspace protocol references.

  • Changed @backstage/plugin-catalog-common from workspace:^ to 0.1.0
  • Changed @backstage/plugin-search-backend-module-techdocs from workspace:^ to 0.2.0
  • Changed @backstage/plugin-search-common from workspace:^ to 0.3.1
  • Changed @backstage/plugin-techdocs-node from workspace:^ to 1.13.11
  • Enables independent package publishing or ensures version stability

@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, aims to enhance the security posture of the project by upgrading several key dependencies within the plugins/techdocs-backend module. The updates are specifically targeted at resolving four identified vulnerabilities, including high-severity arbitrary code injection and directory traversal issues, as well as server-side request forgery. While the dependency versions are bumped, a manual intervention is required to update the yarn.lock file and for projects using Yarn's zero-installs feature.

Highlights

  • Vulnerability Fixes: This pull request addresses and fixes four identified security vulnerabilities: two high-severity issues (Arbitrary Code Injection and Directory Traversal) and two low-severity issues (Server-side Request Forgery).
  • Dependency Updates: Several @backstage related dependencies in plugins/techdocs-backend/package.json have been updated to specific versions to remediate the vulnerabilities. These include @backstage/plugin-catalog-common, @backstage/plugin-search-backend-module-techdocs, @backstage/plugin-search-common, and @backstage/plugin-techdocs-node.
  • Yarn Zero-Installs Warning: Users leveraging Yarn's zero-installs feature will need to manually run yarn after pulling this PR to update the .yarn/cache/ directory, as the PR does not include this update.
  • Manual yarn.lock Update Required: The automated process failed to update the yarn.lock file, which will require a manual update before merging this pull request to ensure dependency consistency.
Changelog
  • plugins/techdocs-backend/package.json
    • Updated @backstage/plugin-catalog-common from workspace:^ to 0.1.0.
    • Updated @backstage/plugin-search-backend-module-techdocs from workspace:^ to 0.2.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 identified security vulnerabilities in the project's dependencies.
  • The PR includes a warning that the yarn.lock file failed to update and requires manual intervention.
  • A note is provided for users of Yarn's zero-installs feature, advising them to run yarn to update their cache.
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.

@entelligence-ai-pr-reviews
Copy link

Walkthrough

This pull request updates the dependency management strategy for the techdocs-backend plugin by replacing workspace protocol references with explicit version numbers. Four Backstage plugin dependencies are pinned to specific versions: @backstage/plugin-catalog-common (0.1.0), @backstage/plugin-search-backend-module-techdocs (0.2.0), @backstage/plugin-search-common (0.3.1), and @backstage/plugin-techdocs-node (1.13.11). This change transitions from monorepo workspace resolution to fixed version dependencies, likely in preparation for independent package publication or to ensure consistent version stability across deployments.

Changes

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

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant PM as Package Manager
    participant TB as techdocs-backend
    participant CC as plugin-catalog-common
    participant SBM as plugin-search-backend-module-techdocs
    participant SC as plugin-search-common
    participant TN as plugin-techdocs-node

    Note over PM,TN: Dependency Resolution Change: Workspace → Fixed Versions

    PM->>TB: Install dependencies
    activate TB
    
    TB->>CC: Require plugin-catalog-common
    Note right of CC: Version: 0.1.0<br/>(was: workspace:^)
    CC-->>TB: Provide catalog interfaces
    
    TB->>SBM: Require search-backend-module-techdocs
    Note right of SBM: Version: 0.2.0<br/>(was: workspace:^)
    SBM-->>TB: Provide search indexing
    
    TB->>SC: Require search-common
    Note right of SC: Version: 0.3.1<br/>(was: workspace:^)
    SC-->>TB: Provide search types
    
    TB->>TN: Require techdocs-node
    Note right of TN: Version: 1.13.11<br/>(was: workspace:^)
    TN-->>TB: Provide techdocs core functionality
    
    deactivate TB
    TB-->>PM: Dependencies resolved with fixed versions

    Note over PM,TN: Impact: Ensures consistent versions across environments
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.

@socket-security
Copy link

@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 typescript under W3C-20150513

License: W3C-20150513 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: LicenseRef-W3C-Community-Final-Specification-Agreement - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: MIT-Khronos-old - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

From: ?npm/@microsoft/api-extractor@7.33.7npm/typescript@4.8.4

ℹ 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/typescript@4.8.4. 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

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 pull request, automatically generated by Snyk, attempts to fix several vulnerabilities by updating dependencies. However, the proposed changes are problematic. It replaces workspace:^ dependencies with pinned versions, which is not ideal for a monorepo. More critically, it downgrades @backstage/plugin-catalog-common and @backstage/plugin-search-common to much older major versions, which will almost certainly break the application. The PR description also notes a failure to update yarn.lock, reinforcing that these changes are incorrect. I recommend rejecting these changes and manually investigating the vulnerabilities to apply the correct updates within the monorepo structure.

Comment on lines +58 to +62
"@backstage/plugin-catalog-common": "0.1.0",
"@backstage/plugin-permission-common": "workspace:^",
"@backstage/plugin-search-backend-module-techdocs": "workspace:^",
"@backstage/plugin-search-common": "workspace:^",
"@backstage/plugin-techdocs-node": "workspace:^",
"@backstage/plugin-search-backend-module-techdocs": "0.2.0",
"@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

These dependency changes are incorrect and will likely break the application.

  1. Incorrect Version Pinning: This PR replaces workspace:^ with pinned versions. In a Yarn workspace monorepo, this is generally incorrect as it breaks the linkage between local packages.
  2. Major Downgrades: The versions for @backstage/plugin-catalog-common (1.0.15 in workspace -> 0.1.0) and @backstage/plugin-search-common (1.2.5 in workspace -> 0.3.1) are significant downgrades. This will likely lead to build failures or runtime errors due to API incompatibilities.
  3. Tooling Failure: The PR description explicitly states Failed to update the yarn.lock, please update manually before merging.. This is a strong indicator that the dependency resolution failed and the suggested versions are not compatible.

Instead of applying these changes, the vulnerabilities should be addressed by updating the source packages within the monorepo if necessary, and then running yarn to update the lockfile. I suggest reverting these changes.

    "@backstage/plugin-catalog-common": "workspace:^",
    "@backstage/plugin-permission-common": "workspace:^",
    "@backstage/plugin-search-backend-module-techdocs": "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