Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade nodemailer from 6.8.0 to 6.9.13 #1008

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

FaroukAmr
Copy link
Owner

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


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

Snyk has created this PR to upgrade nodemailer from 6.8.0 to 6.9.13.

ℹ️ 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 on 2 months ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-NODEMAILER-6219989
586 Proof of Concept
Release notes
Package name: nodemailer
  • 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.7 (2023-10-22)

    Bug Fixes

    • customAuth: Do not require user and pass to be set for custom authentication schemes (fixes #1584) (41d482c)
  • 6.9.6 - 2023-10-09

    6.9.6 (2023-10-09)

    Bug Fixes

    • inline: Use 'inline' as the default Content Dispostion value for embedded images (db32c93)
    • tests: Removed Node v12 from test matrix as it is not compatible with the test framework anymore (7fe0a60)
  • 6.9.5 - 2023-09-06

    6.9.5 (2023-09-06)

    Bug Fixes

    • license: Updated license year (da4744e)
  • 6.9.4 - 2023-07-19

    v6.9.4

  • 6.9.3 - 2023-05-29
  • 6.9.2 - 2023-05-11
  • 6.9.1 - 2023-01-27
  • 6.9.0 - 2023-01-12
  • 6.8.0 - 2022-09-28
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.
  • Snyk has automatically assigned this pull request, set who gets assigned.

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:

Snyk has created this PR to upgrade nodemailer from 6.8.0 to 6.9.13.

See this package in npm:
nodemailer

See this project in Snyk:
https://app.snyk.io/org/faroukamr/project/dc39063e-0f74-4a21-860b-c5ff7f29e1ed?utm_source=github&utm_medium=referral&page=upgrade-pr
@FaroukAmr FaroukAmr self-assigned this May 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

customAuth requires user and pass in credentials
2 participants