[Snyk] Fix for 54 vulnerabilities

[snyk-io]

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

Snyk changed the following file(s):

• packages/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
	Remote Code Execution (RCE) SNYK-JS-MYSQL2-6591085	811
	Arbitrary Code Injection SNYK-JS-MYSQL2-6670046	811
	Incomplete List of Disallowed Inputs SNYK-JS-BABELTRAVERSE-5962462	786
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-8187303	786
	Remote Code Execution (RCE) SNYK-JS-JSONPATHPLUS-7945884	786
	Remote Code Execution (RCE) SNYK-JS-JSONPATHPLUS-8719585	786
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-7577916	776
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-7577917	776
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-7577918	776
	Information Exposure SNYK-JS-ELLIPTIC-8720086	771
	Regular Expression Denial of Service (ReDoS) SNYK-JS-CROSSSPAWN-8303230	756
	Denial of Service (DoS) SNYK-JS-HTTPPROXYMIDDLEWARE-8229906	756
	Regular Expression Denial of Service (ReDoS) SNYK-JS-BABELRUNTIME-10044504	738
	Prototype Pollution SNYK-JS-MYSQL2-6861580	731
	Regular Expression Denial of Service (ReDoS) SNYK-JS-ANSIREGEX-1583908	696
	Regular Expression Denial of Service (ReDoS) SNYK-JS-SEMVER-3247795	696
	Denial of Service (DoS) SNYK-JS-WS-7266574	696
	Regular Expression Denial of Service (ReDoS) SNYK-JS-ZOD-5925617	696
	Path Traversal SNYK-JS-WEBPACKDEVMIDDLEWARE-6476555	691
	Information Exposure Through an Error Message SNYK-JS-BACKSTAGEBACKENDAPPAPI-6229731	686
	Improper Handling of Extra Parameters SNYK-JS-FOLLOWREDIRECTS-6141137	686
	Regular Expression Denial of Service (ReDoS) SNYK-JS-BABELHELPERS-9397697	666
	Regular Expression Denial of Service (ReDoS) SNYK-JS-OCTOKITPLUGINPAGINATEREST-8730855	666
	Regular Expression Denial of Service (ReDoS) SNYK-JS-OCTOKITREQUEST-8730853	666
	Regular Expression Denial of Service (ReDoS) SNYK-JS-OCTOKITREQUESTERROR-8730854	666
	Regular Expression Denial of Service (ReDoS) SNYK-JS-PATHTOREGEXP-7925106	666
	Information Exposure SNYK-JS-FOLLOWREDIRECTS-6444610	646
	Prototype Poisoning SNYK-JS-MYSQL2-6591084	646
	Use of Web Browser Cache Containing Sensitive Information SNYK-JS-MYSQL2-6591300	646
	Server-side Request Forgery (SSRF) SNYK-JS-REQUEST-3361831	646
	Uncontrolled Resource Consumption ('Resource Exhaustion') SNYK-JS-TAR-6476909	646
	Prototype Pollution SNYK-JS-TOUGHCOOKIE-5672873	646
	Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116	631
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-8172694	629
	Cross-site Scripting (XSS) SNYK-JS-SERIALIZEJAVASCRIPT-6147607	626
	Path Traversal SNYK-JS-BACKSTAGEBACKENDCOMMON-6274391	619
	Cross-site Scripting (XSS) SNYK-JS-WEBPACK-7840298	616
	Regular Expression Denial of Service (ReDoS) SNYK-JS-ADOBECSSTOOLS-6096077	589
	Improper Verification of Cryptographic Signature SNYK-JS-BROWSERIFYSIGN-6037026	589
	Inefficient Regular Expression Complexity SNYK-JS-MICROMATCH-6838728	589
	Denial of Service (DoS) SNYK-JS-GRAPHQL-5905181	586
	Cross-site Scripting (XSS) SNYK-JS-ROLLUP-8073097	576
	Regular Expression Denial of Service (ReDoS) SNYK-JS-FASTXMLPARSER-7573289	559
	Always-Incorrect Control Flow Implementation SNYK-JS-HTTPPROXYMIDDLEWARE-9691387	529
	Improper Check for Unusual or Exceptional Conditions SNYK-JS-HTTPPROXYMIDDLEWARE-9691389	529
	Improper Input Validation SNYK-JS-NANOID-8492085	529
	Denial of Service (DoS) SNYK-JS-NWSAPI-2841516	524
	Open Redirect SNYK-JS-EXPRESS-6474509	519
	Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') SNYK-JS-AZUREIDENTITY-7246760	489
	Resource Exhaustion SNYK-JS-JOSE-6419224	479
	Improper Input Validation SNYK-JS-POSTCSS-5926692	479
	Cross-site Scripting SNYK-JS-EXPRESS-7926867	469
	Regular Expression Denial of Service (ReDoS) SNYK-JS-ADOBECSSTOOLS-5871286	464
	Arbitrary Code Injection SNYK-JS-PRISMJS-9055448	436

---

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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
🦉 Information Exposure Through an Error Message
🦉 More lessons are available in Snyk Learn

Summary by Sourcery

Update Backstage backend dependencies to specific versions to address multiple security vulnerabilities

New Features:

• Upgrade Backstage backend plugin modules to specific versions

Bug Fixes:

• Resolve 54 security vulnerabilities in yarn dependencies

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[restack-app]

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]

Reviewer's Guide

This pull request fixes 54 vulnerabilities by updating the versions of three @backstage dependencies in the packages/backend/package.json file. Instead of using workspace-relative versions, these dependencies are now pinned to specific versions. Note that the yarn.lock file was not automatically updated and will require a manual update before merging.

File-Level Changes

Change	Details	Files
Updated versions for several @backstage plugins.	Updated @backstage/plugin-scaffolder-backend-module-confluence-to-markdown from workspace:^ to 0.2.1. Updated @backstage/plugin-scaffolder-backend-module-rails from workspace:^ to 0.1.1. Updated @backstage/plugin-techdocs-backend from workspace:^ to 0.1.1.	packages/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!

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.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​types/​commander@​2.12.2
	@​types/​classnames@​2.3.1
	@​types/​jwt-decode@​3.1.0
	@​types/​ansi-regex@​5.0.0
	@​esbuild/​android-arm64@​0.18.16
	@​esbuild/​darwin-arm64@​0.18.16
	@​esbuild/​darwin-x64@​0.18.16
	@​esbuild/​freebsd-arm64@​0.18.16
	@​esbuild/​freebsd-x64@​0.18.16
	@​esbuild/​linux-arm@​0.18.16
	@​esbuild/​linux-arm64@​0.18.16
	@​esbuild/​linux-ia32@​0.18.16
	@​esbuild/​linux-loong64@​0.18.16
	@​esbuild/​linux-mips64el@​0.18.16
	@​esbuild/​linux-ppc64@​0.18.16
	@​esbuild/​linux-riscv64@​0.18.16
	@​esbuild/​linux-s390x@​0.18.16
	@​esbuild/​linux-x64@​0.18.16
See 494 more rows in the dashboard

View full report

[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!

[snyk-io]

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

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

[graphite-app]

Pinning these dependencies to specific versions (0.2.1 and 0.1.1) while the PR warning indicates the yarn.lock file wasn't updated creates a risk of dependency resolution issues. This approach deviates from the workspace reference pattern used by other dependencies, which could lead to compatibility problems between Backstage components.

Consider either:

1. Maintaining workspace references (workspace:^) and updating yarn.lock properly
2. Ensuring all affected dependencies are pinned consistently with a comprehensive yarn.lock update

This is particularly important in a monorepo structure where components expect consistent versioning across the workspace.

Suggested change

	"@backstage/plugin-scaffolder-backend-module-confluence-to-markdown": "0.2.1",
	"@backstage/plugin-scaffolder-backend-module-rails": "0.1.1",
	"@backstage/plugin-scaffolder-backend-module-confluence-to-markdown": "workspace:^",
	"@backstage/plugin-scaffolder-backend-module-rails": "workspace:^",

Spotted by Diamond

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

[socket-security]

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		@babel/traverse@7.19.1 has a Critical CVE. CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: < 7.23.2 Patched version: 7.23.2 From: storybook/yarn.lock → npm/@babel/helper-module-transforms@7.19.0 → npm/@babel/traverse@7.19.1 ℹ 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/@babel/traverse@7.19.1. 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.
Warn		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.lock → npm/@stoplight/spectral-core@1.18.0 → npm/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]

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!