-
Notifications
You must be signed in to change notification settings - Fork 56
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 mongodb to v4.17.0 [security] #899
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/npm-mongodb-vulnerability
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Branch automerge failureThis PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.
|
renovate
bot
force-pushed
the
renovate/npm-mongodb-vulnerability
branch
from
September 19, 2023 15:09
f9aa5f9
to
8d5c58e
Compare
renovate
bot
force-pushed
the
renovate/npm-mongodb-vulnerability
branch
2 times, most recently
from
September 28, 2023 13:21
efecbc3
to
15e3bc1
Compare
renovate
bot
force-pushed
the
renovate/npm-mongodb-vulnerability
branch
2 times, most recently
from
October 15, 2023 16:42
8f49438
to
57c1807
Compare
renovate
bot
force-pushed
the
renovate/npm-mongodb-vulnerability
branch
from
October 23, 2023 17:53
57c1807
to
edd5496
Compare
renovate
bot
force-pushed
the
renovate/npm-mongodb-vulnerability
branch
from
November 6, 2023 07:11
edd5496
to
d9fa614
Compare
renovate
bot
force-pushed
the
renovate/npm-mongodb-vulnerability
branch
from
November 16, 2023 11:19
d9fa614
to
2bd3430
Compare
renovate
bot
force-pushed
the
renovate/npm-mongodb-vulnerability
branch
from
November 26, 2023 01:42
2bd3430
to
210b58e
Compare
renovate
bot
force-pushed
the
renovate/npm-mongodb-vulnerability
branch
from
December 3, 2023 11:50
210b58e
to
48fc2ce
Compare
renovate
bot
force-pushed
the
renovate/npm-mongodb-vulnerability
branch
from
December 24, 2023 16:24
48fc2ce
to
567971b
Compare
renovate
bot
force-pushed
the
renovate/npm-mongodb-vulnerability
branch
2 times, most recently
from
February 4, 2024 09:51
b0b58bd
to
5a5993b
Compare
renovate
bot
force-pushed
the
renovate/npm-mongodb-vulnerability
branch
from
February 25, 2024 11:13
5a5993b
to
a85d29b
Compare
renovate
bot
force-pushed
the
renovate/npm-mongodb-vulnerability
branch
from
March 12, 2024 09:52
a85d29b
to
8135bca
Compare
renovate
bot
force-pushed
the
renovate/npm-mongodb-vulnerability
branch
2 times, most recently
from
March 24, 2024 15:38
c06fb52
to
33693c2
Compare
renovate
bot
force-pushed
the
renovate/npm-mongodb-vulnerability
branch
2 times, most recently
from
April 21, 2024 11:07
9d3897d
to
ef2fc9d
Compare
renovate
bot
force-pushed
the
renovate/npm-mongodb-vulnerability
branch
from
June 4, 2024 10:29
ef2fc9d
to
a44b701
Compare
renovate
bot
force-pushed
the
renovate/npm-mongodb-vulnerability
branch
from
July 21, 2024 13:23
a44b701
to
2ca5b63
Compare
renovate
bot
force-pushed
the
renovate/npm-mongodb-vulnerability
branch
from
August 6, 2024 10:51
2ca5b63
to
ffd2715
Compare
renovate
bot
force-pushed
the
renovate/npm-mongodb-vulnerability
branch
from
August 28, 2024 07:08
ffd2715
to
b8431c0
Compare
renovate
bot
force-pushed
the
renovate/npm-mongodb-vulnerability
branch
from
October 9, 2024 07:36
b8431c0
to
184a365
Compare
renovate
bot
force-pushed
the
renovate/npm-mongodb-vulnerability
branch
from
December 2, 2024 09:19
184a365
to
d1c0704
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.14.0
->4.17.0
GitHub Vulnerability Alerts
CVE-2021-32050
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
mongodb/node-mongodb-native (mongodb)
v4.17.0
Compare Source
The MongoDB Node.js team is pleased to announce version 4.17.0 of the
mongodb
package!Release Notes
mongodb-js/saslprep
is now installed by defaultUntil v6, the driver included the
saslprep
package as an optional dependency for SCRAM-SHA-256 authentication.saslprep
breaks when bundled with webpack because it attempted to read a file relative to the package location and consequently the driver would throw errors when using SCRAM-SHA-256 if it were bundled.The driver now depends on
mongodb-js/saslprep
, a fork ofsaslprep
that can be bundled with webpack because it includes the necessary saslprep data in memory upon loading. This will be installed by default but will only be used if SCRAM-SHA-256 authentication is used.Remove credential availability on
ConnectionPoolCreatedEvent
In order to avoid mistakenly printing credentials the
ConnectionPoolCreatedEvent
will replace the credentials option with an empty object. The credentials are still accessble via MongoClient options:client.options.credentials
.Features
Bug Fixes
Documentation
We invite you to try the
mongodb
library immediately, and report any issues to the NODE project.v4.16.0
Compare Source
The MongoDB Node.js team is pleased to announce version 4.16.0 of the
mongodb
package!Features
Bug Fixes
Documentation
We invite you to try the
mongodb
library immediately, and report any issues to the NODE project.v4.15.0
Compare Source
The MongoDB Node.js team is pleased to announce version 4.15.0 of the mongodb package!
Features
Bug Fixes
Documentation
We invite you to try the mongodb library immediately, and report any issues to the NODE project.
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.