Skip to content
New issue

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

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

Already on GitHub? # to your account

[Snyk] Upgrade mysql2 from 3.6.5 to 3.11.0 #499

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

Conversation

PugChungus
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade mysql2 from 3.6.5 to 3.11.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 18 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 Prototype Poisoning
SNYK-JS-MYSQL2-6591084
646 Proof of Concept
critical severity Remote Code Execution (RCE)
SNYK-JS-MYSQL2-6591085
646 Proof of Concept
medium severity Use of Web Browser Cache Containing Sensitive Information
SNYK-JS-MYSQL2-6591300
646 Proof of Concept
critical severity Arbitrary Code Injection
SNYK-JS-MYSQL2-6670046
646 Proof of Concept
high severity Prototype Pollution
SNYK-JS-MYSQL2-6861580
646 Proof of Concept
Release notes
Package name: mysql2
  • 3.11.0 - 2024-07-27

    3.11.0 (2024-07-27)

    Features

  • 3.10.3 - 2024-07-15

    3.10.3 (2024-07-15)

    Bug Fixes

  • 3.10.2 - 2024-07-01

    3.10.2 (2024-07-01)

    Bug Fixes

    • typeCast: ensure the same behavior for field.string() with query and execute (#2820) (27e38ea)
  • 3.10.1 - 2024-06-13

    3.10.1 (2024-06-13)

    Bug Fixes

  • 3.10.0 - 2024-05-30

    3.10.0 (2024-05-30)

    Features

    Bug Fixes

    • stream: reads should emit the dataset number for each dataset (#2496, #2628) (4dab4ca)
  • 3.9.9 - 2024-05-29

    3.9.9 (2024-05-29)

    Bug Fixes

    • connection config: remove keepAliveInitialDelay default value (#2712) (688ebab)
  • 3.9.8 - 2024-05-26

    3.9.8 (2024-05-26)

    Bug Fixes

    • security: sanitize fields and tables when using nestTables (#2702) (efe3db5)
    • support deno + caching_sha2_password FULL_AUTHENTICATION_PACKET flow (#2704) (2e03694)
    • typings: typo from jonServerPublicKey to onServerPublicKey (#2699) (8b5f691)
  • 3.9.7 - 2024-04-21

    3.9.7 (2024-04-21)

    Bug Fixes

    • security: sanitize timezone parameter value to prevent code injection - report by zhaoyudi (Nebulalab) (#2608) (7d4b098)
  • 3.9.6 - 2024-04-18

    3.9.6 (2024-04-18)

    Bug Fixes

    • binary parser sometimes reads out of packet bounds when results contain null and typecast is false (#2601) (705835d)
  • 3.9.5 - 2024-04-17

    3.9.5 (2024-04-17)

    Bug Fixes

    • revert breaking change in results creation (#2591) (f7c60d0)
  • 3.9.4 - 2024-04-09
  • 3.9.3 - 2024-03-26
  • 3.9.2 - 2024-02-26
  • 3.9.1 - 2024-01-29
  • 3.9.0 - 2024-01-26
  • 3.8.0 - 2024-01-23
  • 3.7.1 - 2024-01-17
  • 3.7.0 - 2024-01-07
  • 3.6.5 - 2023-11-22
from mysql2 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 mysql2 from 3.6.5 to 3.11.0.

See this package in npm:
mysql2

See this project in Snyk:
https://app.snyk.io/org/ryanleezx/project/a66bdb8e-5826-46a4-b2d6-ccc21c8b6334?utm_source=github&utm_medium=referral&page=upgrade-pr
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants