[Snyk] Upgrade nodemailer from 6.9.3 to 6.10.0

[X-oss-byte]

Snyk has created this PR to upgrade nodemailer from 6.9.3 to 6.10.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 14 versions ahead of your current version.

• The recommended version was released 21 days ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Regular Expression Denial of Service (ReDoS) SNYK-JS-NODEMAILER-6219989	586	Proof of Concept

Release notes

Package name: nodemailer

• 6.10.0 - 2025-01-23
  

  6.10.0 (2025-01-23)

  Features

  • services: add Seznam email service configuration (#1695) (d1ae0a8)

  Bug Fixes

  • proxy: Set error and timeout errors for proxied sockets (aa0c99c)
• 6.9.16 - 2024-10-28
  

  6.9.16 (2024-10-28)

  Bug Fixes

  • addressparser: Correctly detect if user local part is attached to domain part (f2096c5)
• 6.9.15 - 2024-09-03
  

  6.9.15 (2024-08-08)

  Bug Fixes

  • Fix memory leak (#1667) (baa28f6)
  • mime: Added GeoJSON closes #1637 (#1665) (79b8293)
• 6.9.14 - 2024-06-19
  

  6.9.14 (2024-06-19)

  Bug Fixes

  • api: Added support for Ethereal authentication (56b2205)
  • services.json: Add Email Services Provider Feishu Mail (CN) (#1648) (e9e9ecc)
  • services.json: update Mailtrap host and port in well known (#1652) (fc2c9ea)
  • well-known-services: Add Loopia in well known services (#1655) (21a28a1)
• 6.9.13 - 2024-03-20
  

  6.9.13 (2024-03-20)

  Bug Fixes

  • tls: Ensure servername for SMTP (d66fdd3)
• 6.9.12 - 2024-03-08
  

  6.9.12 (2024-03-08)

  Bug Fixes

  • message-generation: Escape single quote in address names (4ae5fad)
• 6.9.11 - 2024-02-29
  

  6.9.11 (2024-02-29)

  Bug Fixes

  • headers: Ensure that Content-type is the bottom header (c7cf97e)
• 6.9.10 - 2024-02-22
  

  6.9.10 (2024-02-22)

  Bug Fixes

  • data-uri: Do not use regular expressions for parsing data URI schemes (12e65e9)
  • data-uri: Moved all data-uri regexes to use the non-regex parseDataUri method (edd5dfe)
• 6.9.9 - 2024-02-01
  

  6.9.9 (2024-02-01)

  Bug Fixes

  • security: Fix issues described in GHSA-9h6g-pr28-7cqp. Do not use eternal matching pattern if only a few occurences are expected (dd8f5e8)
  • tests: Use native node test runner, added code coverage support, removed grunt (#1604) (be45c1b)
• 6.9.8 - 2023-12-30
  

  6.9.8 (2023-12-30)

  Bug Fixes

  • punycode: do not use native punycode module (b4d0e0c)
• 6.9.7 - 2023-10-22
• 6.9.6 - 2023-10-09
• 6.9.5 - 2023-09-06
• 6.9.4 - 2023-07-19
• 6.9.3 - 2023-05-29

from nodemailer GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.
• Max score is 1000. Note that the real score may have changed since the PR was raised.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Summary by Sourcery

Bug Fixes:

• Upgrade nodemailer to v6.10.0 to address a ReDoS vulnerability

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: f86f710

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

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request upgrades the nodemailer dependency from version 6.9.3 to 6.10.0. This upgrade addresses a medium severity Regular Expression Denial of Service (ReDoS) vulnerability. The update involves changes to package.json and package-lock.json to reflect the new version.

Updated class diagram for Nodemailer

classDiagram
  class Nodemailer {
    <<external>>
    +version: string
    +sendMail(options: object, callback: function): void
    +createTransport(options: object): object
  }
  note for Nodemailer "Upgraded from 6.9.3 to 6.10.0\nFixed ReDoS vulnerability\nAdded Seznam email service configuration"

Loading

File-Level Changes

Change	Details	Files
Upgraded the nodemailer dependency to version 6.10.0 to address a Regular Expression Denial of Service (ReDoS) vulnerability.	Updated nodemailer from version 6.9.3 to 6.10.0 in package.json. Updated nodemailer to version 6.10.0 in package-lock.json.	functions/reviewProject/package.json functions/reviewProject/package-lock.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. It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!