[Snyk] Fix for 2 vulnerabilities

[q1blue]

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

Snyk changed the following file(s):

• code/frameworks/server-webpack5/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
	Regular Expression Denial of Service (ReDoS) SNYK-JS-AJV-15274295	803
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-15268416	708

---

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)
🦉 Allocation of Resources Without Limits or Throttling

[gemini-code-assist]

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the project's security by resolving two identified vulnerabilities. It achieves this by updating specific Storybook-related dependencies within the server-webpack5 framework's package.json file, ensuring the project benefits from the latest security patches.

Highlights

• Vulnerability Fixes: Addressed two security vulnerabilities: a high-severity Regular Expression Denial of Service (ReDoS) (SNYK-JS-AJV-15274295) and a medium-severity Allocation of Resources Without Limits or Throttling (SNYK-JS-QS-15268416).
• Dependency Updates: Updated @storybook/builder-webpack5 to version 6.2.0 and @storybook/preset-server-webpack to version 7.0.0 in code/frameworks/server-webpack5/package.json.

Changelog

• code/frameworks/server-webpack5/package.json
  • Updated @storybook/builder-webpack5 dependency from workspace:* to 6.2.0.
  • Updated @storybook/preset-server-webpack dependency from workspace:* to 7.0.0.

Activity

• This pull request was automatically created by Snyk to address identified vulnerabilities.
• Snyk reported a failure to update the yarn.lock file, indicating a manual update is required before merging.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, aims to fix two security vulnerabilities by updating dependencies. However, the proposed changes introduce a significant risk. The dependencies @storybook/builder-webpack5 and @storybook/preset-server-webpack are being downgraded by multiple major versions, from workspace:* (which resolves to version 8.3.0-beta.3 in this monorepo) to 6.2.0 and 7.0.0 respectively. This is a major breaking change and is very likely to cause issues. Furthermore, the PR description notes that yarn.lock was not updated, which is a critical step that must be performed manually. Due to the high risk of breakage from the dependency downgrade, this PR should be handled with extreme caution. It is advisable to reject this automated fix and address the vulnerabilities by other means.

[gemini-code-assist]

This change downgrades @storybook/builder-webpack5 from the current workspace version (8.3.0-beta.3) to 6.2.0 and @storybook/preset-server-webpack from 8.3.0-beta.3 to 7.0.0. Pinning to older major versions instead of using workspace:* in a monorepo is highly likely to cause breaking changes and runtime errors, as packages within the workspace are expected to be compatible. This automated fix seems incorrect for this project structure. A better approach would be to address the underlying vulnerabilities in the transitive dependencies without downgrading major versions of core packages.