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.

Sign up for GitHub

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

Jump to bottom

🚨 [security] [backend] Update mongoose 6.0.8 → 6.12.8 (minor) #314

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

🚨 [security] [backend] Update mongoose 6.0.8 → 6.12.8 (minor) #314

wants to merge 1 commit into from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Apr 23, 2024

🚨 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 update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ mongoose (6.0.8 → 6.12.8) · Repo · Changelog

Security Advisories 🚨

🚨 Mongoose Prototype Pollution vulnerability

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

🚨 Mongoose Vulnerable to Prototype Pollution in Schema Object

Description

Mongoose is a MongoDB object modeling tool designed to work in an asynchronous environment.

Affected versions of this package are vulnerable to Prototype Pollution. The Schema.path() function is vulnerable to prototype pollution when setting the schema object. This vulnerability allows modification of the Object prototype and could be manipulated into a Denial of Service (DoS) attack.

Proof of Concept

// poc.js
const mongoose = require('mongoose');
const schema = new mongoose.Schema();

malicious_payload = 'proto.toString'


schema.path(malicious_payload, [String])


x = {}

console.log(x.toString()) // crashed (Denial of service (DoS) attack)

Impact

This vulnerability can be manipulated to exploit other types of attacks, such as Denial of service (DoS), Remote Code Execution, or Property Injection.

🚨 automattic/mongoose vulnerable to Prototype pollution via Schema.path

Mongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. Affected versions of this package are vulnerable to Prototype Pollution. The Schema.path() function is vulnerable to prototype pollution when setting the schema object. This vulnerability allows modification of the Object prototype and could be manipulated into a Denial of Service (DoS) attack.

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.

↗️ @​types/node (indirect, 16.10.1 → 20.12.7) · Repo

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

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

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

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

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

↗️ bson (indirect, 4.5.2 → 4.7.2) · Repo · Changelog

Release Notes

4.7.2

The MongoDB Node.js team is pleased to announce version v4.7.2 of the bson package!

Bug Fixes

Documentation

We invite you to try the bson library immediately, and report any issues to the NODE project.

4.7.1

The MongoDB Node.js team is pleased to announce version v4.7.1 of the bson package!

Bug Fixes

Documentation

We invite you to try the bson library immediately, and report any issues to the NODE project.

4.7.0

The MongoDB Node.js team is pleased to announce version 4.7.0 of the bson package!

Release Highlights

This release adds automatic UUID support. Now when serializing or deserializing BSON you can work directly with the UUID type without explicit conversion methods. The UUID class is now a subclass of binary so all existing code will continue to work (including the explicit conversion methods .toUUID/.toBinary). The same automatic support for UUID is also present in EJSON .parse/.stringify.

Take a look at the following for the expected behavior:

const document = BSON.deserialize(bytes)
// { uuid: UUID('xxx') }
BSON.serialize(document)
// Buffer < document with uuid (binary subtype 4) >

Special thanks to @aditi-khare-mongoDB for all her hard work on this feature!! 🎉

Features

Documentation

We invite you to try the bson library immediately, and report any issues to the NODE project.

4.6.5

The MongoDB Node.js team is pleased to announce version 4.6.5 of the bson package!

Release Highlights

Along with some other bug fixes listed below in this release we've fixed the float parser logic for both deserialize and serialize to use JS Dataview APIs. The most delightful part of this change is an improvement to performance of serializing 64-bit floats. 🎉 🐎

- cpu: Apple M1
- cores: 8
- os: darwin
- ram: 16GB
- iterations: 1,000,000
testing: Double Serialization
current           - v 4.6.5 - avg 0.00024913ms
previous release  - v 4.6.4 - avg 0.00036335ms
previous major    - v 1.1.6 - avg 0.00036459ms

Bug Fixes

Documentation

We invite you to try the bson library immediately, and report any issues to the NODE project.

4.6.4

The MongoDB Node.js team is pleased to announce version 4.6.4 of the bson package!

Performance

  • perf(NODE-4194): improve objectId constructor performance (#498)

Documentation

We invite you to try the bson library immediately, and report any issues to the NODE project.

4.6.3

The MongoDB Node.js team is pleased to announce version 4.6.3 of the bson package!

Release Highlights

This release improves documentation for BSON type classes by adding an @category tag to the doc comments.

Documentation

We invite you to try the bson library immediately, and report any issues to the NODE project.

4.6.2

The MongoDB Node.js team is pleased to announce version 4.6.2 of the bson package!

Release Highlights

This release includes a few fixes to the ObjectId class, including performance improvements in ObjectId.equals.

Bug Fixes

Documentation

We invite you to try the bson library immediately, and report any issues to the NODE project.

4.6.1

The MongoDB Node.js team is pleased to announce version 4.6.1 of the bson package!

Release Highlights

This release includes a few fixes to the validation checks in some of our constructors.

Bug Fixes

Documentation

We invite you to try the bson library immediately, and report any issues to the NODE project.

4.6.0

The MongoDB Node.js team is pleased to announce version 4.6.0 of the bson package!

Release Highlights

This release adds a new BSON validation option that allows top-level keys to have utf-8 validation disabled or enabled, either on a global or key-specific scale, rather than defaulting to automatic utf-8 validation across all keys. Additionally, it includes a bug fix which allows BSONError and BSONTypeError to be checked with instanceof checks.

Features

Bug Fixes

Documentation

We invite you to try the bson library immediately, and report any issues to the NODE project.

4.5.4

The MongoDB Node.js team is pleased to announce version 4.5.4 of the bson package!

Release Highlights

This release notably includes a fix to the ObjectId constructor ensuring correct handling of invalid input.

Bug Fixes

Documentation

We invite you to try the bson library immediately, and report any issues to the NODE project.

4.5.3

The MongoDB Node.js team is pleased to announce version 4.5.3 of the bson package!

Release Highlights

This release includes a few minor changes for spec compliance, primarily around validation, as detailed below:

Bug Fixes

Documentation

We invite you to try the bson 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 more commits than we can show here.

↗️ kareem (indirect, 2.3.2 → 2.5.1) · Repo · Changelog

Commits

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

↗️ mongodb (indirect, 4.1.1 → 4.17.2) · 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).

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.1.0 → 2.6.0) · Repo

Commits

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

↗️ mpath (indirect, 0.8.4 → 0.9.0) · Repo · Changelog

Release Notes

0.9.0 (from changelog)

  • feat: export stringToParts()

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

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

Release Notes

4.0.3 (from changelog)

  • fix: allow using comment with findOneAndUpdate(), count(), distinct() and hint with findOneAndUpdate() Automattic/mongoose#11793

4.0.2 (from changelog)

  • perf: replace regexp-clone with native functionality #131 Uzlopak

4.0.1 (from changelog)

4.0.0 / 2021-08-24

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

Commits

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

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

Commits

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

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

Release Notes

16.0.0 (from changelog)

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

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

Commits

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

↗️ webidl-conversions (indirect, 6.1.0 → 7.0.0) · Repo

Commits

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

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

Release Notes

11.0.0

The breaking changes in this release are only to the Low-level URL Standard API. No actual URL parsing or serialization behavior has changed, and users of the URL and URLSearchParams exports are not affected.

These changes follow whatwg/url@fbaa03c.

  • Removed the URL record type's cannotBeABaseURL property.
  • Changed the URL record type's path from always being an array of strings, to being either a single string or an array of strings.
  • Renamed the "cannot-be-a-base-URL path" parser state (i.e. value for stateOverride) to "opaque path".
  • Added the serializePath(urlRecord) export.
  • Added the hasAnOpaquePath(urlRecord) export.

10.0.0

The breaking changes in this release are to the API exported by the whatwg-url/webidl2js-wrapper module. In particular it now is based on webidl2js v17, which changes some of the exported function signatures, and changes the realms of any errors thrown on misuse.

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

Commits

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

🆕 @​aws-crypto/ie11-detection (added, 3.0.0)

🆕 @​aws-crypto/sha256-browser (added, 3.0.0)

🆕 @​aws-crypto/sha256-js (added, 3.0.0)

🆕 @​aws-crypto/supports-web-crypto (added, 3.0.0)

🆕 @​aws-crypto/util (added, 3.0.0)

🆕 @​aws-sdk/client-cognito-identity (added, 3.556.0)

🆕 @​aws-sdk/client-sso (added, 3.556.0)

🆕 @​aws-sdk/client-sso-oidc (added, 3.556.0)

🆕 @​aws-sdk/client-sts (added, 3.556.0)

🆕 @​aws-sdk/core (added, 3.556.0)

🆕 @​aws-sdk/credential-provider-cognito-identity (added, 3.556.0)

🆕 @​aws-sdk/credential-provider-env (added, 3.535.0)

🆕 @​aws-sdk/credential-provider-http (added, 3.552.0)

🆕 @​aws-sdk/credential-provider-ini (added, 3.556.0)

🆕 @​aws-sdk/credential-provider-node (added, 3.556.0)

🆕 @​aws-sdk/credential-provider-process (added, 3.535.0)

🆕 @​aws-sdk/credential-provider-sso (added, 3.556.0)

🆕 @​aws-sdk/credential-provider-web-identity (added, 3.556.0)

🆕 @​aws-sdk/credential-providers (added, 3.556.0)

🆕 @​aws-sdk/middleware-host-header (added, 3.535.0)

🆕 @​aws-sdk/middleware-logger (added, 3.535.0)

🆕 @​aws-sdk/middleware-recursion-detection (added, 3.535.0)

🆕 @​aws-sdk/middleware-user-agent (added, 3.540.0)

🆕 @​aws-sdk/region-config-resolver (added, 3.535.0)

🆕 @​aws-sdk/token-providers (added, 3.556.0)

🆕 @​aws-sdk/types (added, 3.535.0)

🆕 @​aws-sdk/util-endpoints (added, 3.540.0)

🆕 @​aws-sdk/util-locate-window (added, 3.535.0)

🆕 @​aws-sdk/util-user-agent-browser (added, 3.535.0)

🆕 @​aws-sdk/util-user-agent-node (added, 3.535.0)

🆕 @​aws-sdk/util-utf8-browser (added, 3.259.0)

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

🆕 @​smithy/abort-controller (added, 2.2.0)

🆕 @​smithy/config-resolver (added, 2.2.0)

🆕 @​smithy/core (added, 1.4.2)

🆕 @​smithy/credential-provider-imds (added, 2.3.0)

🆕 @​smithy/fetch-http-handler (added, 2.5.0)

🆕 @​smithy/hash-node (added, 2.2.0)

🆕 @​smithy/invalid-dependency (added, 2.2.0)

🆕 @​smithy/is-array-buffer (added, 2.2.0)

🆕 @​smithy/middleware-content-length (added, 2.2.0)

🆕 @​smithy/middleware-endpoint (added, 2.5.1)

🆕 @​smithy/middleware-retry (added, 2.3.1)

🆕 @​smithy/middleware-serde (added, 2.3.0)

🆕 @​smithy/middleware-stack (added, 2.2.0)

🆕 @​smithy/node-config-provider (added, 2.3.0)

🆕 @​smithy/node-http-handler (added, 2.5.0)

🆕 @​smithy/property-provider (added, 2.2.0)

🆕 @​smithy/protocol-http (added, 3.3.0)

🆕 @​smithy/querystring-builder (added, 2.2.0)

🆕 @​smithy/querystring-parser (added, 2.2.0)

🆕 @​smithy/service-error-classification (added, 2.1.5)

🆕 @​smithy/shared-ini-file-loader (added, 2.4.0)

🆕 @​smithy/signature-v4 (added, 2.3.0)

🆕 @​smithy/smithy-client (added, 2.5.1)

🆕 @​smithy/types (added, 2.12.0)

🆕 @​smithy/url-parser (added, 2.2.0)

🆕 @​smithy/util-base64 (added, 2.3.0)

🆕 @​smithy/util-body-length-browser (added, 2.2.0)

🆕 @​smithy/util-body-length-node (added, 2.3.0)

🆕 @​smithy/util-buffer-from (added, 2.2.0)

🆕 @​smithy/util-config-provider (added, 2.3.0)

🆕 @​smithy/util-defaults-mode-browser (added, 2.2.1)

🆕 @​smithy/util-defaults-mode-node (added, 2.3.1)

🆕 @​smithy/util-endpoints (added, 1.2.0)

🆕 @​smithy/util-hex-encoding (added, 2.2.0)

🆕 @​smithy/util-middleware (added, 2.2.0)

🆕 @​smithy/util-retry (added, 2.2.0)

🆕 @​smithy/util-stream (added, 2.2.0)

🆕 @​smithy/util-uri-escape (added, 2.2.0)

🆕 @​smithy/util-utf8 (added, 2.3.0)

🆕 bowser (added, 2.11.0)

🆕 fast-xml-parser (added, 4.2.5)

🆕 ip-address (added, 9.0.5)

🆕 jsbn (added, 1.1.0)

🆕 smart-buffer (added, 4.2.0)

🆕 socks (added, 2.8.3)

🆕 sprintf-js (added, 1.1.3)

🆕 strnum (added, 1.0.5)

🆕 tslib (added, 2.6.2)

🆕 undici-types (added, 5.26.5)

🆕 uuid (added, 9.0.1)

🗑️ denque (removed)

🗑️ regexp-clone (removed)

🗑️ saslprep (removed)

🗑️ sliced (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)

@depfu depfu bot added the depfu label Apr 23, 2024
@depfu depfu bot mentioned this pull request Apr 23, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
depfu
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants