Skip to content

[Snyk] Fix for 16 vulnerabilities#4531

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

[Snyk] Fix for 16 vulnerabilities#4531
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-23b8803a34c1da5e63e6a10c2e32c0d8

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io Bot commented Apr 12, 2025

snyk-top-banner

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

Snyk changed the following file(s):

  • plugins/catalog-backend-module-bitbucket-cloud/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 Regular Expression Denial of Service (ReDoS)
SNYK-JS-CROSSSPAWN-8303230
  756  
high severity Server-side Request Forgery (SSRF)
SNYK-JS-IP-6240864
  751  
high severity Symlink Attack
SNYK-JS-TARFS-9535930
  721  
high severity Excessive Platform Resource Consumption within a Loop
SNYK-JS-BRACES-6838727
  696  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-OCTOKITREQUEST-8730853
  666  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-OCTOKITREQUESTERROR-8730854
  666  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-PATHTOREGEXP-7925106
  666  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-PATHTOREGEXP-8482416
  666  
medium severity Server-Side Request Forgery (SSRF)
SNYK-JS-IP-7148531
  646  
medium severity Uncontrolled Resource Consumption ('Resource Exhaustion')
SNYK-JS-TAR-6476909
  646  
medium severity Missing Release of Resource after Effective Lifetime
SNYK-JS-INFLIGHT-6095116
  631  
high severity Asymmetric Resource Consumption (Amplification)
SNYK-JS-BODYPARSER-7926860
  624  
medium severity Denial of Service (DoS)
SNYK-JS-GRAPHQL-5905181
  586  
medium severity Cross-site Scripting (XSS)
SNYK-JS-COOKIE-8163060
  529  
low severity Cross-site Scripting
SNYK-JS-SEND-7926862
  319  
low severity Cross-site Scripting
SNYK-JS-SERVESTATIC-7926865
  319  

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:

🦉 Cross-site Scripting (XSS)
🦉 Regular Expression Denial of Service (ReDoS)
🦉 Server-side Request Forgery (SSRF)

Summary by Sourcery

Update dependencies to fix multiple security vulnerabilities in the Backstage Bitbucket Cloud catalog backend module

Bug Fixes:

  • Resolve 16 security vulnerabilities across various dependencies, including potential ReDoS, SSRF, and XSS issues

Enhancements:

  • Update package dependencies to specific versions to address security concerns

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Apr 12, 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 Apr 12, 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 Apr 12, 2025

Reviewer's Guide by Sourcery

This pull request updates the versions of @backstage/backend-tasks, @backstage/plugin-bitbucket-cloud-common, and @backstage/plugin-catalog-common in plugins/catalog-backend-module-bitbucket-cloud/package.json to address 16 security vulnerabilities.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Updates versions of multiple packages to address security vulnerabilities.
  • Updates @backstage/backend-tasks from workspace:^ to 0.6.1.
  • Updates @backstage/plugin-bitbucket-cloud-common from workspace:^ to 0.1.0.
  • Updates @backstage/plugin-catalog-common from workspace:^ to 0.1.0.
plugins/catalog-backend-module-bitbucket-cloud/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 +50 to +56
"@backstage/backend-tasks": "0.6.1",
"@backstage/catalog-client": "workspace:^",
"@backstage/catalog-model": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/integration": "workspace:^",
"@backstage/plugin-bitbucket-cloud-common": "workspace:^",
"@backstage/plugin-catalog-common": "workspace:^",
"@backstage/plugin-bitbucket-cloud-common": "0.1.0",
"@backstage/plugin-catalog-common": "0.1.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.

Caution: Replacing workspace references with pinned versions

This change replaces workspace:^ references with specific version numbers (0.6.1 and 0.1.0), which fundamentally changes how dependencies are resolved in this Yarn workspace.

In a monorepo setup:

  • workspace:^ ensures local development versions are used
  • Pinned versions fetch from external registry instead of using local code

This approach may cause:

  • Version mismatches between local development and production
  • Integration issues with other workspace packages
  • Difficulty testing local changes across packages

Consider either:

  1. Maintaining the workspace references for development flexibility
  2. Ensuring these specific versions are fully compatible with all other packages in the monorepo
  3. Implementing a more comprehensive strategy for vulnerability management that preserves workspace integrity
Suggested change
"@backstage/backend-tasks": "0.6.1",
"@backstage/catalog-client": "workspace:^",
"@backstage/catalog-model": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/integration": "workspace:^",
"@backstage/plugin-bitbucket-cloud-common": "workspace:^",
"@backstage/plugin-catalog-common": "workspace:^",
"@backstage/plugin-bitbucket-cloud-common": "0.1.0",
"@backstage/plugin-catalog-common": "0.1.0",
"@backstage/backend-tasks": "workspace:^",
"@backstage/catalog-client": "workspace:^",
"@backstage/catalog-model": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/integration": "workspace:^",
"@backstage/plugin-bitbucket-cloud-common": "workspace:^",
"@backstage/plugin-catalog-common": "workspace:^",

Spotted by Diamond

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

@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 Apr 19, 2025
@github-actions github-actions Bot closed this Apr 28, 2025
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.

0 participants