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

fix(deps): update dependency mysql2 to v3.9.8 [security] #13632

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 30, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
mysql2 (source) 3.9.7 -> 3.9.8 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2024-21512

Versions of the package mysql2 before 3.9.8 are vulnerable to Prototype Pollution due to improper user input sanitization passed to fields and tables when using nestTables.


Release Notes

sidorares/node-mysql2 (mysql2)

v3.9.8

Compare Source

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)

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Copy link
Contributor Author

renovate bot commented May 30, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: sample/07-sequelize/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"0.2.1" from the root project
npm ERR!   peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/common
npm ERR!     @nestjs/common@"10.3.2" from the root project
npm ERR!     peer @nestjs/common@"^10.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/core
npm ERR!       @nestjs/core@"10.3.2" from the root project
npm ERR!       3 more (@nestjs/platform-express, @nestjs/sequelize, @nestjs/testing)
npm ERR!     3 more (@nestjs/platform-express, @nestjs/sequelize, @nestjs/testing)
npm ERR!   2 more (@nestjs/core, sequelize-typescript)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/sequelize
npm ERR!   @nestjs/sequelize@"10.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/sequelize
npm ERR!     @nestjs/sequelize@"10.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-06-03T11_39_39_842Z-debug-0.log

@renovate renovate bot added the dependencies Pull requests that update a dependency file label May 30, 2024
@renovate renovate bot force-pushed the renovate/npm-mysql2-vulnerability branch 2 times, most recently from a04d73d to 47c5da7 Compare June 3, 2024 10:49
@coveralls
Copy link

coveralls commented Jun 3, 2024

Pull Request Test Coverage Report for Build a85bc410-2a47-42d6-be7f-be0325a64c5f

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 92.191%

Totals Coverage Status
Change from base Build 9d9da93e-7f5b-4bc4-a816-0e63c0a28502: 0.0%
Covered Lines: 6741
Relevant Lines: 7312

💛 - Coveralls

@renovate renovate bot force-pushed the renovate/npm-mysql2-vulnerability branch from 47c5da7 to bb3ebe1 Compare June 3, 2024 11:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant