Skip to content

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Jan 16, 2025


🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!


Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ mongoose (6.8.2 → 8.9.5) · Repo · Changelog

Security Advisories 🚨

🚨 Mongoose search injection vulnerability

Mongoose before 8.9.5 can improperly use a nested $where filter with a populate() match, leading to search injection. NOTE: this issue exists because of an incomplete fix for CVE-2024-53900.

🚨 Mongoose search injection vulnerability

Mongoose versions prior to 8.8.3, 7.8.3, and 6.13.5 are vulnerable to improper use of the $where operator. This vulnerability arises from the ability of the $where clause to execute arbitrary JavaScript code in MongoDB queries, potentially leading to code injection attacks and unauthorized access or manipulation of database data.

🚨 Mongoose search injection vulnerability

Mongoose versions prior to 8.8.3, 7.8.3, and 6.13.5 are vulnerable to improper use of the $where operator. This vulnerability arises from the ability of the $where clause to execute arbitrary JavaScript code in MongoDB queries, potentially leading to code injection attacks and unauthorized access or manipulation of database data.

🚨 Mongoose search injection vulnerability

Mongoose versions prior to 8.8.3, 7.8.3, and 6.13.5 are vulnerable to improper use of the $where operator. This vulnerability arises from the ability of the $where clause to execute arbitrary JavaScript code in MongoDB queries, potentially leading to code injection attacks and unauthorized access or manipulation of database data.

🚨 Mongoose Prototype Pollution vulnerability

Prototype Pollution in GitHub repository automattic/mongoose prior to 7.3.3, 6.11.3, and 5.13.20.

🚨 Mongoose Prototype Pollution vulnerability

Prototype Pollution in GitHub repository automattic/mongoose prior to 7.3.3, 6.11.3, and 5.13.20.

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by 10 commits:

↗️ @​types/webidl-conversions (indirect, 7.0.0 → 7.0.3) · Repo

Sorry, we couldn't find anything useful about this release.

↗️ @​types/whatwg-url (indirect, 8.2.2 → 11.0.5) · Repo

Sorry, we couldn't find anything useful about this release.

↗️ bson (indirect, 4.7.0 → 6.10.1) · Repo · Changelog

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ kareem (indirect, 2.5.0 → 2.6.3) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 18 commits:

↗️ mongodb (indirect, 4.12.1 → 6.12.0) · Repo · Changelog

Security Advisories 🚨

🚨 MongoDB Driver may publish events containing authentication-related data

Some MongoDB Drivers may erroneously publish events containing authentication-related data to a command listener configured by an application. The published events may contain security-sensitive data when specific authentication-related commands are executed.

Without due care, an application may inadvertently expose this sensitive information, e.g., by writing it to a log file. This issue only arises if an application enables the command listener feature (this is not enabled by default).

This issue affects the MongoDB C Driver 1.0.0 prior to 1.17.7, MongoDB PHP Driver 1.0.0 prior to 1.9.2, MongoDB Swift Driver 1.0.0 prior to 1.1.1, MongoDB Node.js Driver 3.6 prior to 3.6.10, MongoDB Node.js Driver 4.0 prior to 4.17.0 and MongoDB Node.js Driver 5.0 prior to 5.8.0. This issue also affects users of the MongoDB C++ Driver dependent on the C driver 1.0.0 prior to 1.17.7 (C++ driver prior to 3.7.0).

🚨 MongoDB Driver may publish events containing authentication-related data

Some MongoDB Drivers may erroneously publish events containing authentication-related data to a command listener configured by an application. The published events may contain security-sensitive data when specific authentication-related commands are executed.

Without due care, an application may inadvertently expose this sensitive information, e.g., by writing it to a log file. This issue only arises if an application enables the command listener feature (this is not enabled by default).

This issue affects the MongoDB C Driver 1.0.0 prior to 1.17.7, MongoDB PHP Driver 1.0.0 prior to 1.9.2, MongoDB Swift Driver 1.0.0 prior to 1.1.1, MongoDB Node.js Driver 3.6 prior to 3.6.10, MongoDB Node.js Driver 4.0 prior to 4.17.0 and MongoDB Node.js Driver 5.0 prior to 5.8.0. This issue also affects users of the MongoDB C++ Driver dependent on the C driver 1.0.0 prior to 1.17.7 (C++ driver prior to 3.7.0).

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ mongodb-connection-string-url (indirect, 2.6.0 → 3.0.2) · Repo · Changelog

Release Notes

3.0.2

3.0.2 (2025-01-14)

The MongoDB Node.js team is pleased to announce version 3.0.2 of the mongodb-connection-string-url package!

Release Notes

This release updates the whatwg-url dependency to either be 13.x or 14.x as either works with this package. Ensuring you have 14 installed in your dependency tree should address the deprecation warning related to 'punycode'

We invite you to try the mongodb-connection-string-url library immediately, and report any issues to the NODE project.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 21 commits:

↗️ mquery (indirect, 4.0.3 → 5.0.0) · Repo · Changelog

Release Notes

5.0.0 (from changelog)

  • BREAKING CHANGE: drop callback support #137 hasezoey
  • BREAKING CHANGE: remove custom promise library support #137 hasezoey
  • BREAKING CHANGE: remove long deprecated update, remove functions #136 hasezoey
  • BREAKING CHANGE: remove collection ducktyping: first param to mquery() is now always the query filter #138
  • feat: support MongoDB Node driver 5 #137 hasezoey

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 53 commits:

↗️ punycode (indirect, 2.1.1 → 2.3.1) · Repo

Commits

See the full diff on Github. The new version differs by 25 commits:

↗️ sift (indirect, 16.0.1 → 17.1.3) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 2 commits:

↗️ tr46 (indirect, 3.0.0 → 5.0.0) · Repo

Commits

See the full diff on Github. The new version differs by 17 commits:

↗️ whatwg-url (indirect, 11.0.0 → 14.1.0) · Repo

Release Notes

14.1.0

Added URL.parse(), per whatwg/url@58acb06.

14.0.0

Breaking change: removed Node.js v16 support.

13.0.0

Breaking change: removed Node.js v14 support.

Added URL.canParse(), per whatwg/url@ae3c28b.

Added URLSearchParams's size getter, per whatwg/url@12b6f0c.

Added optional second value argument to URLSearchParams's has() and delete() methods, per whatwg/url@bfb9157.

Changed the serialization of the origin of blob: URLs whose inner URLs were not http: or https: to be "null", per whatwg/url@eee49fd.

12.0.1

Updated our tr46 dependency, which brings along several fixes related to international domain names. Such as:

  • Empty domain name labels, as in https://xn--4-0bd15808a.../, no longer cause URL parsing to fail.
  • Invalid punycode-encoded domain name labels, as in http://xn--ls8h=/, now correctly cause URL parsing to fail.
  • Includes support for Unicode 15.0.0.

As part of this, we are now running against the newly-introduced test data derived from the Unicode Consortium-maintained IdnaTestV2.txt file, and passing them all.

12.0.0

Breaking change: removed Node.js v12 support.

Changed the characters allowed in domains vs. generic hosts, per whatwg/url@35e195a.

Changed the URL API's search and hash setters, as well as the URLSearchParams API, to always ensure the URL is serialize-parse roundtrippable, per whatwg/url@fdaa0e5.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 43 commits:

🆕 @​mongodb-js/saslprep (added, 1.1.9)

🗑️ @​aws-crypto/ie11-detection (removed)

🗑️ @​aws-crypto/sha256-browser (removed)

🗑️ @​aws-crypto/sha256-js (removed)

🗑️ @​aws-crypto/supports-web-crypto (removed)

🗑️ @​aws-crypto/util (removed)

🗑️ @​aws-sdk/abort-controller (removed)

🗑️ @​aws-sdk/client-cognito-identity (removed)

🗑️ @​aws-sdk/client-sso (removed)

🗑️ @​aws-sdk/client-sso-oidc (removed)

🗑️ @​aws-sdk/client-sts (removed)

🗑️ @​aws-sdk/config-resolver (removed)

🗑️ @​aws-sdk/credential-provider-cognito-identity (removed)

🗑️ @​aws-sdk/credential-provider-env (removed)

🗑️ @​aws-sdk/credential-provider-imds (removed)

🗑️ @​aws-sdk/credential-provider-ini (removed)

🗑️ @​aws-sdk/credential-provider-node (removed)

🗑️ @​aws-sdk/credential-provider-process (removed)

🗑️ @​aws-sdk/credential-provider-sso (removed)

🗑️ @​aws-sdk/credential-provider-web-identity (removed)

🗑️ @​aws-sdk/credential-providers (removed)

🗑️ @​aws-sdk/fetch-http-handler (removed)

🗑️ @​aws-sdk/hash-node (removed)

🗑️ @​aws-sdk/invalid-dependency (removed)

🗑️ @​aws-sdk/is-array-buffer (removed)

🗑️ @​aws-sdk/middleware-content-length (removed)

🗑️ @​aws-sdk/middleware-endpoint (removed)

🗑️ @​aws-sdk/middleware-host-header (removed)

🗑️ @​aws-sdk/middleware-logger (removed)

🗑️ @​aws-sdk/middleware-recursion-detection (removed)

🗑️ @​aws-sdk/middleware-retry (removed)

🗑️ @​aws-sdk/middleware-sdk-sts (removed)

🗑️ @​aws-sdk/middleware-serde (removed)

🗑️ @​aws-sdk/middleware-signing (removed)

🗑️ @​aws-sdk/middleware-stack (removed)

🗑️ @​aws-sdk/middleware-user-agent (removed)

🗑️ @​aws-sdk/node-config-provider (removed)

🗑️ @​aws-sdk/node-http-handler (removed)

🗑️ @​aws-sdk/property-provider (removed)

🗑️ @​aws-sdk/protocol-http (removed)

🗑️ @​aws-sdk/querystring-builder (removed)

🗑️ @​aws-sdk/querystring-parser (removed)

🗑️ @​aws-sdk/service-error-classification (removed)

🗑️ @​aws-sdk/shared-ini-file-loader (removed)

🗑️ @​aws-sdk/signature-v4 (removed)

🗑️ @​aws-sdk/smithy-client (removed)

🗑️ @​aws-sdk/token-providers (removed)

🗑️ @​aws-sdk/types (removed)

🗑️ @​aws-sdk/url-parser (removed)

🗑️ @​aws-sdk/util-base64 (removed)

🗑️ @​aws-sdk/util-body-length-browser (removed)

🗑️ @​aws-sdk/util-body-length-node (removed)

🗑️ @​aws-sdk/util-buffer-from (removed)

🗑️ @​aws-sdk/util-config-provider (removed)

🗑️ @​aws-sdk/util-defaults-mode-browser (removed)

🗑️ @​aws-sdk/util-defaults-mode-node (removed)

🗑️ @​aws-sdk/util-endpoints (removed)

🗑️ @​aws-sdk/util-hex-encoding (removed)

🗑️ @​aws-sdk/util-locate-window (removed)

🗑️ @​aws-sdk/util-middleware (removed)

🗑️ @​aws-sdk/util-retry (removed)

🗑️ @​aws-sdk/util-uri-escape (removed)

🗑️ @​aws-sdk/util-user-agent-browser (removed)

🗑️ @​aws-sdk/util-user-agent-node (removed)

🗑️ @​aws-sdk/util-utf8-browser (removed)

🗑️ @​aws-sdk/util-utf8-node (removed)

🗑️ @​types/node (removed)

🗑️ base64-js (removed)

🗑️ bowser (removed)

🗑️ buffer (removed)

🗑️ fast-xml-parser (removed)

🗑️ ieee754 (removed)

🗑️ ip (removed)

🗑️ saslprep (removed)

🗑️ smart-buffer (removed)

🗑️ socks (removed)

🗑️ strnum (removed)

🗑️ tslib (removed)

🗑️ uuid (removed)


👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants