Skip to content

[Snyk] Fix for 1 vulnerabilities#4470

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

[Snyk] Fix for 1 vulnerabilities#4470
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-2b6b291002d6f69e2fa29bf81a019e5f

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io Bot commented Mar 29, 2025

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):

  • plugins/stack-overflow-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 Symlink Attack
SNYK-JS-TARFS-9535930
  721  

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.

Summary by Sourcery

Update dependencies to fix a high-severity Snyk vulnerability in the stack-overflow-backend plugin

Bug Fixes:

  • Fix a high-severity Symlink Attack vulnerability (SNYK-JS-TARFS-9535930) by updating package dependencies

Enhancements:

  • Update @backstage/backend-common from workspace version to 0.24.1
  • Update @backstage/plugin-search-common from workspace version to 0.3.1

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Mar 29, 2025

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@restack-app
Copy link
Copy Markdown

restack-app Bot commented Mar 29, 2025

No applications have been configured for previews targeting branch: master. To do so go to restack console and configure your applications for previews.

@sourcery-ai
Copy link
Copy Markdown

sourcery-ai Bot commented Mar 29, 2025

Reviewer's Guide by Sourcery

This pull request updates the @backstage/backend-common and @backstage/plugin-search-common dependencies in plugins/stack-overflow-backend/package.json to address a high severity Symlink Attack vulnerability (SNYK-JS-TARFS-9535930). The versions were updated from workspace:^ to 0.24.1 and 0.3.1 respectively.

Updated class diagram for package.json dependencies

classDiagram
  class PackageJson {
    dependencies
  }

  PackageJson --|> BackendCommon
  PackageJson --|> PluginSearchCommon

  class BackendCommon {
    -version: string = "0.24.1"
  }
  note for BackendCommon "Updated from workspace:^"

  class PluginSearchCommon {
    -version: string = "0.3.1"
  }
  note for PluginSearchCommon "Updated from workspace:^"
Loading

File-Level Changes

Change Details Files
Updated @backstage/backend-common and @backstage/plugin-search-common dependencies to address a high severity vulnerability.
  • Upgraded @backstage/backend-common from workspace:^ to 0.24.1.
  • Upgraded @backstage/plugin-search-common from workspace:^ to 0.3.1.
plugins/stack-overflow-backend/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!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

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

Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

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

We have skipped reviewing this pull request. Here's why:

  • It seems to have been created by a bot (hey, snyk-io[bot]!). We assume it knows what it's doing!
  • It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
  • We don't review packaging changes - Let us know if you'd like us to change this.

Comment on lines +35 to +37
"@backstage/backend-common": "0.24.1",
"@backstage/config": "workspace:^",
"@backstage/plugin-search-common": "workspace:^",
"@backstage/plugin-search-common": "0.3.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.

Replacing workspace references with fixed versions in a monorepo can lead to dependency resolution conflicts. This approach breaks the internal dependency management that workspace references provide, where packages automatically use the latest local versions.

The PR description also indicates that the yarn.lock file wasn't updated properly. Before merging, it's important to:

  1. Run yarn to regenerate the lockfile with these changes
  2. Consider whether fixed versions are appropriate in this context - typically in monorepos, workspace references (workspace:^) are used intentionally to ensure internal packages stay in sync

If the vulnerability fix is necessary, consider upgrading the affected dependencies while maintaining workspace references, or follow your team's established approach for handling security updates in the monorepo.

Suggested change
"@backstage/backend-common": "0.24.1",
"@backstage/config": "workspace:^",
"@backstage/plugin-search-common": "workspace:^",
"@backstage/plugin-search-common": "0.3.1",
"@backstage/backend-common": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/plugin-search-common": "workspace:^",

Spotted by Diamond

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

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 5, 2025

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 Apr 5, 2025
@github-actions github-actions Bot closed this Apr 10, 2025
@snyk-io snyk-io Bot reopened this Jun 24, 2025
@snyk-io
Copy link
Copy Markdown
Author

snyk-io Bot commented Jun 24, 2025

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

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

@socket-security
Copy link
Copy Markdown

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 for details)
Warn Critical
jsonpath-plus@7.1.0 has a Critical CVE.

CVE: GHSA-pppg-cpfq-h7wr JSONPath Plus Remote Code Execution (RCE) Vulnerability (CRITICAL)

Affected versions: < 10.2.0

Patched version: 10.2.0

From: yarn.locknpm/@stoplight/spectral-core@1.18.0npm/jsonpath-plus@7.1.0

ℹ Read more on: This package | This alert | What is a critical CVE?

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: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/jsonpath-plus@7.1.0. 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

@github-actions github-actions Bot removed the stale label Jun 25, 2025
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jul 7, 2025

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 Jul 7, 2025
@github-actions github-actions Bot closed this Jul 15, 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