Skip to content

Comments

[Snyk] Security upgrade nodemailer from 6.9.7 to 6.9.9#1602

Open
warrenchristian1telus wants to merge 1 commit intomainfrom
snyk-fix-f13d4b69629a3c5efd63e28c18859a0d
Open

[Snyk] Security upgrade nodemailer from 6.9.7 to 6.9.9#1602
warrenchristian1telus wants to merge 1 commit intomainfrom
snyk-fix-f13d4b69629a3c5efd63e28c18859a0d

Conversation

@warrenchristian1telus
Copy link
Collaborator

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:
    • forms-flow-forms/package.json
    • forms-flow-forms/package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
medium severity 658/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-JS-NODEMAILER-6219989
No Proof of Concept

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

Commit messages
Package name: nodemailer The new version differs by 11 commits.

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:

🦉 Regular Expression Denial of Service (ReDoS)

…on to reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-NODEMAILER-6219989
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.

2 participants