MongoDB Node.js driver version 3.6.3 introduces subtle but important updates compared to the preceding 3.6.2 release, primarily impacting the development environment and its tooling. The core dependencies remain consistent, indicating that the fundamental functionalities of interacting with MongoDB databases are unchanged. However, developers upgrading to 3.6.3 will notice adjustments in the *devDependencies* section.
Notably, the eslint version jumps from 4.5.0 to 7.10.0, suggesting a significant upgrade in code linting and style enforcement. This aligns the driver with more modern JavaScript coding standards and best practices, potentially catching a wider range of coding errors or stylistic inconsistencies. The eslint-plugin-prettier also sees an update, moving from version 2.2.0 to 3.1.3, further enhancing code formatting and consistency. Furthermore, version 3.6.3 introduces a new *devDependency*: eslint-plugin-es "^3.0.1".
The releaseDate reveals that v3.6.3 was released in November 2020, approximately two months after v3.6.2. The slight increase in unpackedSize (from 1478572 to 1481512) hints at minor additions or adjustments within the codebase, possibly related to the updated tooling. For developers, deciding whether to upgrade hinges on their development workflow and reliance on these specific linting and formatting tools. If a project already leverages a similar ESLint configuration, the upgrade might be seamless. However, projects using older configurations should carefully review the new ESLint rules to avoid introducing unexpected errors or warnings.
All the vulnerabilities related to the version 3.6.3 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).
