[Snyk] Fix for 1 vulnerabilities

[snyk-io]

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

Snyk changed the following file(s):

• microsite/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
	Server-side Request Forgery (SSRF) SNYK-JS-AXIOS-9403194	596

---

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:

🦉 Server-side Request Forgery (SSRF)

Summary by Sourcery

Bug Fixes:

• Fix a Server-Side Request Forgery (SSRF) vulnerability by upgrading @docusaurus/core and @docusaurus/preset-classic to version 3.0.1.

[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 by Sourcery

This pull request updates the @docusaurus/core and @docusaurus/preset-classic dependencies in microsite/package.json to version 3.0.1. This resolves a Server-Side Request Forgery (SSRF) vulnerability.

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

File-Level Changes

Change	Details	Files
Updated @docusaurus/core and @docusaurus/preset-classic dependencies to version 3.0.1 to address a Server-Side Request Forgery (SSRF) vulnerability.	Updated @docusaurus/core from 0.0.0-5591 to 3.0.1. Updated @docusaurus/preset-classic from 0.0.0-5591 to 3.0.1.	microsite/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

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

[sourcery-ai]

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.

[socket-security]

Report too large to display inline

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Known malware	npm/@babel/plugin-transform-typeof-symbol@7.18.9	Note: Malicious code in plugin-transform-typeof-symbol (npm) Source: ghsa-malware (2d37e14c9688f52a303b8670134fee30325028b9e1c7cf0ca5c0873e69ed3016) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.	microsite/yarn.lock	🚫
Known malware	npm/@babel/preset-modules@0.1.5	Note: Malicious code in preset-modules (npm) Source: ghsa-malware (bce4d502bf9ab093c7d390d5b71812207dacb59531230032226826562d298eca) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.	microsite/yarn.lock	🚫
Known malware	npm/@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@7.18.9	Note: Malicious code in plugin-bugfix-v8-spread-parameters-in-optional-chaining (npm) Source: ghsa-malware (fb0d774f7cfd02ac60a020ca20356ef2dbef57e366ef6f38ccfda5e1ed532f14) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.	microsite/yarn.lock	🚫
Known malware	npm/@azure/core-auth@1.4.0	Note: Malicious code in core-auth (npm) Source: ghsa-malware (6bdfd71008501f118552100797abf6fb298f1db14a272dda22ede246874ef20c) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.	yarn.lock	🚫
Known malware	npm/@smithy/node-config-provider@1.0.2	Note: Malicious code in node-config-provider (npm) Source: ghsa-malware (6245de88dda255b54977801c4cb54ca206cf3e832670277220fba95bf3707455) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.	yarn.lock	🚫
Known malware	npm/@smithy/smithy-client@1.0.4	Note: Malicious code in smithy-client (npm) Source: ghsa-malware (a3ca6db1d2e1b3b5d4cc263af07ad3bdac1620be7e66c259231937ba10ad755c) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.	yarn.lock	🚫
Critical CVE	npm/@babel/traverse@7.19.1	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	microsite/yarn.lock	⚠︎
Known malware	npm/@babel/plugin-syntax-flow@7.16.7	Note: Malicious code in plugin-syntax-flow (npm) Source: ghsa-malware (04e8baeb56984ab713bfa2788f7884ef46499c9b336153a61ffc4051c39c4dd4) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.	storybook/yarn.lock	🚫
Known malware	npm/@babel/plugin-transform-react-jsx@7.18.6	Note: Malicious code in plugin-transform-react-jsx (npm) Source: ghsa-malware (f27c2a663077678179b48cd4851aa8b5aa144a1d4ef1e3bb2cf05526d0b1c7c7) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.	microsite/yarn.lock	🚫
Critical CVE	npm/jsonpath-plus@7.1.0	CVE: GHSA-pppg-cpfq-h7wr JSONPath Plus Remote Code Execution (RCE) Vulnerability (CRITICAL) Affected versions: < 10.2.0 Patched version: 10.2.0	packages/repo-tools/package.json yarn.lock	⚠︎
Known malware	npm/@azure/core-rest-pipeline@1.9.2	Note: Malicious code in core-rest-pipeline (npm) Source: ghsa-malware (4396b5e4255c98c3adaa6e8c6927ef76c435d214321de5910eb4970c541e85d2) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.	yarn.lock	🚫
Known malware	npm/@azure/msal-node@1.17.3	Note: Malicious code in msal-node (npm) Source: ghsa-malware (3e629627b7937f8d6f569de9b7ca1983194dd52f6d325a6d52fd1b69a678fc43) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.	yarn.lock	🚫
Known malware	npm/@azure/core-http@3.0.0	Note: Malicious code in core-http (npm) Source: ghsa-malware (0fad0636caa74d3861dc3c386532f949aff7cd7ce8da43ea64ae46bcccc24a1b) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.	yarn.lock	🚫

View full report↗︎

Next steps

What is known malware?

This package is malware. We have asked the package registry to remove it.

It is strongly recommended that malware is removed from your codebase.

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/@babel/plugin-transform-typeof-symbol@7.18.9
• @SocketSecurity ignore npm/@babel/preset-modules@0.1.5
• @SocketSecurity ignore npm/@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@7.18.9
• @SocketSecurity ignore npm/@azure/core-auth@1.4.0
• @SocketSecurity ignore npm/@smithy/node-config-provider@1.0.2
• @SocketSecurity ignore npm/@smithy/smithy-client@1.0.4
• @SocketSecurity ignore npm/@babel/traverse@7.19.1
• @SocketSecurity ignore npm/@babel/plugin-syntax-flow@7.16.7
• @SocketSecurity ignore npm/@babel/plugin-transform-react-jsx@7.18.6
• @SocketSecurity ignore npm/jsonpath-plus@7.1.0
• @SocketSecurity ignore npm/@azure/core-rest-pipeline@1.9.2
• @SocketSecurity ignore npm/@azure/msal-node@1.17.3
• @SocketSecurity ignore npm/@azure/core-http@3.0.0

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