Version 3.6.7 of the "mongodb" Node.js driver introduces subtle yet important updates compared to version 3.6.6. Developers should primarily note changes in the development dependencies, reflecting improvements in the driver's build process and testing infrastructure. The upgrade includes newer versions of key tools like typescript (from potentially absent in version 3.6.6 to ^4.2.4) and @types/node (from absent in version 3.6.6 to ^14.14.37), indicating a focus on enhanced TypeScript support and compatibility with more recent Node.js versions. A new dependency tslib at version ^2.2.0 suggests a stronger integration with TypeScript projects.
Furthermore, standard-version is bumped up (from ^8.0.2 to ^9.2.0), streamlining release management. The introduction of nyc (^15.1.0) points towards improved code coverage reporting. While the core functionalities and dependencies remain largely consistent, this release emphasizes developer experience through tooling upgrades. The optional-require dependency is updated from 1.0.2 to ^1.0.3. Also the dist section shows differences in releaseDate, filecount and unpacked size which can be relevant to some more specific use cases. Developers working with TypeScript or requiring detailed code coverage metrics will find version 3.6.7 particularly beneficial. These updates enhance the driver's maintainability and integration with modern development workflows.
All the vulnerabilities related to the version 3.6.7 of the package
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).
