[Snyk] Security upgrade mysql2 from 2.3.3 to 3.9.7

[kingjay66]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • docs/recipes/docker-server/package.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	883/1000 Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 9.8	Arbitrary Code Injection SNYK-JS-MYSQL2-6670046	Yes	Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: mysql2

The new version differs by 250 commits.

• 2d3cad8 chore(master): release 3.9.7 (#2609)
• 7d4b098 fix(security): sanitize timezone parameter value to prevent code injection (#2608)
• 2efd6ab build(deps): bump lucide-react from 0.371.0 to 0.372.0 in /website (#2606)
• e3391ed build(deps): bump lucide-react from 0.368.0 to 0.371.0 in /website (#2604)
• 4f58caa chore(master): release 3.9.6 (#2603)
• 705835d fix: binary parser sometimes reads out of packet bounds when results contain null and typecast is false (#2601)
• 2129818 chore(master): release 3.9.5 (#2600)
• f7c60d0 fix: revert breaking change in results creation (#2591)
• 7f5b395 build(deps-dev): bump @ typescript-eslint/eslint-plugin in /website (#2596)
• a770052 build(deps-dev): bump @ typescript-eslint/parser in /website (#2595)
• 6dccf55 build(deps): bump lucide-react from 0.367.0 to 0.368.0 in /website (#2590)
• 9190db9 build(deps): bump sass from 1.74.1 to 1.75.0 in /website (#2589)
• 00f483f build(deps-dev): bump typescript from 5.4.4 to 5.4.5 (#2587)
• c95d661 build(deps-dev): bump typescript from 5.4.3 to 5.4.5 in /website (#2586)
• b72cac3 build(deps): bump lucide-react from 0.364.0 to 0.367.0 in /website (#2583)
• c45fb6f build(deps-dev): bump @ types/node from 20.12.4 to 20.12.7 (#2582)
• 407b9eb build(deps-dev): bump @ typescript-eslint/parser in /website (#2579)
• ad7de60 build(deps-dev): bump @ typescript-eslint/eslint-plugin in /website (#2578)
• cf3fa60 chore(master): release 3.9.4 (#2566)
• 4a964a3 fix(security): improve results object creation (#2574)
• 71115d8 ci: improve parser tests (#2573)
• 74abf9e fix(security): improve supportBigNumbers and bigNumberStrings sanitization (#2572)
• 8a818ce fix(docs): improve the contribution guidelines (#2552)
• 0f08c7c build(deps-dev): bump @ docusaurus/tsconfig in /website (#2563)

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

---

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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Arbitrary Code Injection

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/ms@2.1.2	None	0	6.84 kB	styfle

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
New author	npm/ms@2.1.2	New Author: styfle Previous Author: leo

View full report↗︎

Next steps

What is new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

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/ms@2.1.2