[Snyk] Fix for 2 vulnerabilities

[q1blue]

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

Snyk changed the following file(s):

• packages/email-server/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Server-side Request Forgery (SSRF) SNYK-JS-AXIOS-9292519	310
	Server-side Request Forgery (SSRF) SNYK-JS-AXIOS-9403194	215

---

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)

[changeset-bot]

⚠️ No Changeset found

Latest commit: a78bb92

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​tidb-community/​tracking-script@​0.1.0
	npm/​@​docusaurus/​module-type-aliases@​2.1.0
	npm/​@​djagger/​echartsx@​0.0.22
	npm/​@​docusaurus/​preset-classic@​2.1.0
	npm/​@​docusaurus/​plugin-google-gtag@​2.1.0
	npm/​@​stackql/​docusaurus-plugin-hubspot@​1.0.1
	npm/​@​types/​grecaptcha@​3.0.4
	npm/​@​docusaurus/​plugin-client-redirects@​2.1.0
	npm/​@​tsconfig/​docusaurus@​1.0.6
	npm/​@​types/​webpack-env@​1.18.0
	npm/​@​docusaurus/​theme-search-algolia@​2.1.0
	npm/​@​docusaurus/​core@​2.1.0
	npm/​@​emotion/​server@​11.10.0
	npm/​@​types/​d3-hierarchy@​3.1.0
	npm/​@​primer/​octicons-react@​16.3.1
	npm/​@​geo-maps/​countries-land-10km@​0.6.0
	npm/​@​types/​luxon@​3.3.8 ⏵ 2.4.0			+1
	npm/​@​makotot/​ghostui@​2.0.0
	npm/​@​sentry/​tracing@​7.16.0
	npm/​country-code-emoji@​2.3.0
	npm/​@​types/​is-hotkey@​0.1.7
	npm/​ace-builds@​1.12.3
	npm/​clsx@​1.2.1
	npm/​@​types/​react-copy-to-clipboard@​5.0.4
	npm/​deepmerge@​4.3.1 ⏵ 4.2.2
	npm/​babel-plugin-direct-import@​1.0.0
	npm/​echarts-for-react@​3.0.2
	npm/​is-hotkey@​0.2.0
	npm/​chartjs-plugin-datalabels@​2.1.0
	npm/​animate.css@​4.1.1
See 23 more rows in the dashboard

View full report

[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		npm/@babel/[email protected] 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; >= 8.0.0-alpha.0 < 8.0.0-alpha.4 Patched version: 7.23.2 From: web/package-lock.json → npm/@emotion/[email protected] → npm/@emotion/[email protected] → npm/@docusaurus/[email protected] → npm/@docusaurus/[email protected] → npm/@docusaurus/[email protected] → npm/@docusaurus/[email protected] → npm/@docusaurus/[email protected] → npm/@babel/[email protected] ℹ 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 [email protected]. 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/[email protected]. 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		npm/[email protected] has Obfuscated code. Confidence: 0.95 Location: Package overview From: web/package-lock.json → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? 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 [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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		npm/[email protected] has a License Policy Violation. License: CC-BY-4.0 (npm metadata) License: CC-BY-4.0 (package/LICENSE) License: CC-BY-4.0 (package/package.json) From: web/package-lock.json → npm/@emotion/[email protected] → npm/@emotion/[email protected] → npm/@docusaurus/[email protected] → npm/@docusaurus/[email protected] → npm/@docusaurus/[email protected] → npm/@docusaurus/[email protected] → npm/@docusaurus/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? 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 [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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