Skip to content

Conversation

@snyk-bot
Copy link

Snyk has created this PR to upgrade node-mailjet from 3.2.1 to 3.3.7.

ℹ️ 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 8 versions ahead of your current version.
  • The recommended version was released 23 days ago, on 2022-02-16.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Remote Code Execution (RCE)
SNYK-JS-PACRESOLVER-1564857
726/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
Proof of Concept
Server-side Request Forgery (SSRF)
SNYK-JS-NETMASK-1089716
726/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
Proof of Concept
Prototype Pollution
SNYK-JS-JSONBIGINT-608659
726/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
Proof of Concept

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

Release notes
Package name: node-mailjet
  • 3.3.7 - 2022-02-16

    Fix vulnerable dependencies in main project

  • 3.3.6 - 2022-02-16

    3.3.6

  • 3.3.5 - 2022-01-20

    What's Changed

    New Contributors

    Full Changelog: v3.3.3...v3.3.5

  • 3.3.4 - 2021-05-22
  • 3.3.3 - 2021-05-21
    No content.
  • 3.3.2 - 2021-05-21
  • 3.3.1 - 2018-10-15

    Perform api call - now return Promise in order to be the same as real Mailjet api call
    Error handling - able to get status, response and reason and return proper error message

  • 3.3.0 - 2018-10-01
  • 3.2.1 - 2017-07-25

    Fixed incorrect published package.json on NPM

from node-mailjet GitHub release notes
Commit messages
Package name: node-mailjet

Compare


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

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

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