Skip to content

[Snyk] Fix for 3 vulnerabilities#5609

Closed
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-e781b9ef1b927cb33b34cf1697304da8
Closed

[Snyk] Fix for 3 vulnerabilities#5609
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-e781b9ef1b927cb33b34cf1697304da8

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io Bot commented Jun 5, 2025

snyk-top-banner

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

Snyk changed the following file(s):

  • packages/dev-utils/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 Origin Validation Error
SNYK-JS-WEBPACKDEVSERVER-10300775
  748  
high severity Improper Link Resolution Before File Access ('Link Following')
SNYK-JS-TARFS-10293725
  721  
medium severity Exposed Dangerous Method or Function
SNYK-JS-WEBPACKDEVSERVER-10300777
  693  

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:

🦉 Improper Link Resolution Before File Access ('Link Following')

Summary by Sourcery

Upgrade three @backstage dependencies in dev-utils to fixed versions to remediate reported security vulnerabilities.

Bug Fixes:

  • Bump @backstage/core-components to version 0.1.0 to address high-severity vulnerabilities.
  • Bump @backstage/integration-react to version 0.1.1 to address high-severity vulnerabilities.
  • Bump @backstage/plugin-catalog-react to version 0.0.1 to address medium-severity vulnerabilities.

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Jun 5, 2025

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@sourcery-ai
Copy link
Copy Markdown

sourcery-ai Bot commented Jun 5, 2025

Reviewer's Guide

This auto-generated PR replaces three workspace-scoped @backstage dependencies in packages/dev-utils/package.json with explicit patched versions to resolve high- and medium-severity vulnerabilities and requires a manual yarn.lock update before merging.

File-Level Changes

Change Details Files
Pin dev-utils dependencies to patched versions
  • Bump @backstage/core-components from workspace: to 0.1.0
  • Bump @backstage/integration-react from workspace: to 0.1.1
  • Bump @backstage/plugin-catalog-react from workspace: to 0.0.1
packages/dev-utils/package.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Comment on lines +38 to +41
"@backstage/core-components": "0.1.0",
"@backstage/core-plugin-api": "workspace:^",
"@backstage/integration-react": "workspace:^",
"@backstage/plugin-catalog-react": "workspace:^",
"@backstage/integration-react": "0.1.1",
"@backstage/plugin-catalog-react": "0.0.1",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The pinned versions (0.1.0, 0.1.1, 0.0.1) are unusually old for security fixes, which raises concerns about compatibility with other workspace dependencies. This approach deviates from the typical workspace reference pattern used throughout the rest of the file.

Additionally, the PR notes that the yarn.lock file failed to update automatically and requires manual updating before merging. This is a critical step for these security fixes to take effect properly.

Consider:

  1. Updating to more recent versions that address the vulnerabilities
  2. Ensuring compatibility with other workspace dependencies
  3. Manually updating the yarn.lock file as indicated in the PR description

These steps will help ensure the security fixes are applied effectively without introducing new compatibility issues.

Suggested change
"@backstage/core-components": "0.1.0",
"@backstage/core-plugin-api": "workspace:^",
"@backstage/integration-react": "workspace:^",
"@backstage/plugin-catalog-react": "workspace:^",
"@backstage/integration-react": "0.1.1",
"@backstage/plugin-catalog-react": "0.0.1",
"@backstage/core-components": "workspace:^",
"@backstage/core-plugin-api": "workspace:^",
"@backstage/integration-react": "workspace:^",
"@backstage/plugin-catalog-react": "workspace:^",

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

@snyk-io
Copy link
Copy Markdown
Author

snyk-io Bot commented Jun 5, 2025

Snyk checks have failed. 1 issues have been found so far.

Icon Severity Issues
Critical 0
High 0
Medium 1
Low 0

security/snyk check is complete. 1 issues have been found. (View Details)

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

@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 Jun 12, 2025
@github-actions github-actions Bot closed this Jun 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants