[Snyk] Fix for 2 vulnerabilities

[snyk-io]

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

Snyk changed the following file(s):

• plugins/catalog-backend-module-bitbucket-server/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
	Origin Validation Error SNYK-JS-WEBPACKDEVSERVER-10300775	748
	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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Summary by Sourcery

Upgrade key Backstage dependencies in the Bitbucket Server catalog backend module to address two vulnerabilities in webpack-dev-server.

Bug Fixes:

• Bump @backstage/backend-common to 0.24.1 to include patched webpack-dev-server.
• Upgrade @backstage/catalog-model to 0.1.1 to resolve exposed dangerous method vulnerability.
• Update @backstage/plugin-catalog-node to 1.0.0 to fix origin validation error vulnerability.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[sourcery-ai]

Reviewer's Guide

This PR replaces three workspace version specifiers with explicit fixed releases in the Bitbucket Server catalog backend’s package.json to remediate high- and medium-severity webpack-dev-server vulnerabilities — ensure the lockfile is also updated manually before merging.

Sequence Diagram for Snyk Vulnerability Remediation Process

sequenceDiagram
    actor Snyk
    participant ProjectRepository
    participant Developer

    Snyk->>ProjectRepository: Scans dependencies for vulnerabilities
    activate ProjectRepository
    Snyk->>ProjectRepository: Creates PR (updates package.json for 2 vulnerabilities)
    ProjectRepository-->>Snyk: PR created with updated dependencies
    deactivate ProjectRepository
    Snyk->>Developer: Notifies: PR ready for review
    Snyk->>Developer: Action Required: Update yarn.lock manually

Loading

File-Level Changes

Change	Details	Files
Upgrade workspace dependencies to fixed versions	Set @backstage/backend-common to 0.24.1 Set @backstage/catalog-model to 0.1.1 Set @backstage/plugin-catalog-node to 1.0.0	plugins/catalog-backend-module-bitbucket-server/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

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[snyk-io]

⛔ 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.

[graphite-app]

The version 0.1.1 specified for @backstage/catalog-model appears to be significantly outdated and inconsistent with the other upgraded dependencies (backend-common@0.24.1 and plugin-catalog-node@1.0.0). This version discrepancy will likely cause compatibility issues during installation or runtime.

In the Backstage ecosystem, package versions typically align more closely. The catalog-model package should have a version that's compatible with the other core packages being updated in this PR.

Consider verifying the correct version of catalog-model that works with the specified versions of backend-common and plugin-catalog-node before merging this security fix.

Suggested change

	"@backstage/catalog-model": "0.1.1",
	"@backstage/catalog-model": "^1.4.0",

Spotted by Diamond

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

[github-actions]

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!