The MongoDB Node.js driver experienced a minor version update from 4.0.1 to 4.1.0, representing incremental improvements and potentially bug fixes rather than a major overhaul. Both versions share the same core dependencies, including "bson," "denque," "saslprep," and "mongodb-connection-string-url," indicating that the fundamental data handling and connection mechanisms remain consistent.
The development dependencies, crucial for building, testing, and documentation, are also identical across both versions. This suggests a continuity in the development workflow and tools used by the MongoDB team. Libraries for linting ("eslint"), testing ("mocha," "chai," "sinon"), documentation ("jsdoc," "typedoc"), and TypeScript support are all present in both.
Looking at the "dist" section of each package provides some hints regarding the changes. The "fileCount" increases from 298 in version 4.0.1 to 301 in version 4.1.0, and the "unpackedSize" grows from 2,799,934 bytes to 2,875,210 bytes. This means that the newest version includes a few more files and has obviously added some small features or functionalities that required some extra KBs. Developers should expect similar performance and API stability but may benefit from subtle enhancements or resolved edge cases. Given the minor version bump, a review of the official release notes and changelog provided by MongoDB is highly recommended to uncover the specific changes. The newer version shows that the MongoDB team is active and dedicated to improving the official MongoDB driver for Node.js.
All the vulnerabilities related to the version 4.1.0 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).
